Menu
I couldn't find anything what is the "right" approach to manage the releases using git. Say, I have master, release-1, release-2 and release-3 branches. Release 1 is already released and I do only bugfixing and released versions tagging on it. Release 2 is going to be released soon and I develop mostly on this branch while on 3 I develop things which will be needed in the further future.
When I add some feature on release-2 and it should go to 3 as well, but not to 1, should I:
When I need to changes sth in all the versions, should I do it on master and cherry-pick it to all the branches?
Should I keep master up to date with the newest(release-3 branch) or rather developer on release-3 and merge to the master just before I will need release-4 branch?
When I fix sth on release-1 or release-2, should I merge or cherry-pick it to master or rather?
I'm not quite sure when should I cherry-pick, when should I merge and if the flow of the code between the branches it right.
736
On GitHub.com, navigate to the main page of the repository. To the right of the list of files, click Releases. On the right side of the page, next to the release you want to edit, click . Edit the details for the release in the form, then click Update release.
Releases are first-class objects with changelogs. and binary assets that present a full project history beyond Git artifacts. They're accessible from a repository's homepage: Releases are accompanied by release notes and links to download the software. or source code.
At their core, Releases are based on Git tags. Tags mark a specific point in the history of your project, so they're a great way to indicate a Release. Releases are ordered by a tag's date in the following way: If it's an annotated tag, the tag object's date is used.
No, currently it's not possible to have public releases in a private repository. Yes, you can use the API to check if there's a new release -- use the releases API: developer.github.com/v3/repos/releases.
See the following posts on Junio C Hamano (git maintainer) blog:
Take also look at gitworkflows manual page.
96
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
