![]() ![]() It's just that, for structured tags, it seems like an extra step. Fetching all branches and tags from a remote Git repository Christoph Petersen 1 min read Fetch everything: git fetch -all In my first days at HorseAnalytics, one of the first tasks was to review the codebase and streamline the build and release process. I know that the git tag can be called out explicitly in the dependency definition. Best case, I'm guessing there's other related requirements, which should be considered. can name an arbitrary remote ref (for example, the name of a tag) or even a collection of refs with corresponding remote-tracking branches (e.g.![]() If useful, the regex used to match the tags could be configurable, to support different tag naming schemes. And 'dep = 1.0' would implicitly fetch all tags, and select the tag with a patch release of the highest value (ex. Is reasonable to propose an optional feature where Cargo would checkout the corresponding git tag, based on the Cargo version specified for the dependency?įor example, 'dep = "1.0.0' would checkout the tag 'v1.0.0'. I'm working with repos where we have a 1:1 relationship between Cargo versions and git tags, where the tags are nearly the same as the Cargo semver string (ex. I have the same desire as to improve git dependency handling in Cargo. ![]() I was just about to start a new thread on this same topic, but happened to dig up this old one. ![]()
0 Comments
Leave a Reply. |