feat: Checkout tags as well as branches when cloning into scratch#1482
Open
feat: Checkout tags as well as branches when cloning into scratch#1482
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1482 +/- ##
==========================================
- Coverage 95.21% 95.19% -0.02%
==========================================
Files 43 43
Lines 3132 3123 -9
==========================================
- Hits 2982 2973 -9
Misses 150 150 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The branch field in the config file can now be set to the value of a
tag. While it could be confusing to use 'branch' for both, it mirrors
the behaviour of the
--branchflag when cloning repositories with thegit CLI.
In a slight change in behaviour, the branch field is now only used when
first cloning a repository - if it already exists in the scratch area it
will be left in the same state. This is to avoid the ambiguity of how
tags should behave when the repo has been modified since being cloned.