Feature history view #105
Open
Feature history view #105
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added extract file and folder annotations for feature history, optimized methods,fixed parsing commit diffs logic
johmara
requested changes
Nov 29, 2024
src/main/java/se/isselab/HAnS/featureLocation/FeatureLocationManager.java
Outdated
Show resolved
Hide resolved
…HistoryView # Conflicts: # src/main/java/se/isselab/HAnS/featureLocation/FeatureLocationManager.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Introduced a new Feature History functionality with annotations and code. This feature is designed to track the evolution of features across commits, utilizing three types of annotations: code annotations, file mappings, and folder mappings.
Motivation and Context
Currently, developers still face problems in managing feature evolution, because traditional version control systems like Git track changes to code files but lack support for feature-level changes. Visualizing feature history might help with tracking the changes of features, without completely relying on Git's CLI to track these changes manually.
How Has This Been Tested?
This code was tested with the Snake project
Types of changes
Checklist: