-
Notifications
You must be signed in to change notification settings - Fork 314
Improve Git commit info building #9210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
6b3cf19
feat: add single command to obtain full commit info
daniel-mohedano bef1740
feat: update soft unshallow to use --no-write-fetch
daniel-mohedano 25dbcbb
chore: remove unused getAuthor..., getCommitter..., and getFullMessage
daniel-mohedano 815a095
style: spotless
daniel-mohedano d4526f8
chore: renamed field to headCommit for clarity
daniel-mohedano 50f0421
feat: add pr number parsing for github actions file
daniel-mohedano 13a176f
fix: treat pr.number as `Number` for github actions parsing
daniel-mohedano 72f9b91
fix: simplify pr.number extraction
daniel-mohedano 0f0698d
refactor: rename and refactor to clarify the unshallow execution paths
daniel-mohedano 9c4c478
feat: add check for presence of commit before unshallowing
daniel-mohedano ef249c8
refactor: separate fetching and unshallowing functionality
daniel-mohedano fa81bea
renaming
daniel-mohedano 004fc73
refactor: move commitFetch and isCommitPresent to private methods
daniel-mohedano File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure if the
gitClient.isShallow()needs to be updated to check if the provided commit SHA is present. Also, what happens if we request unshallow with a commit SHA, and then request "full unshallow" with anullSHA?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will look into updating the logic to check
isShallowfor a specific commit if the argument is provided. Could avoid additional git cmd calls that are unnecessary if it is called repeatedly. Regarding the two calls, AFAIK the second "full unshallow" would just be executed as regular, unshallowing to theshallow-sincelimit, given that theisShallowcheck would be true.