BLD: use release branches#954
Merged
Merged
Conversation
ColmTalbot
reviewed
May 12, 2025
ColmTalbot
left a comment
Collaborator
There was a problem hiding this comment.
I'm happy with this change, and the docs generally look good. I just had a question about the GUI vs CLI approaches.
|
|
||
| If making a major or minor release you must first make the release branch from the current `main` branch | ||
|
|
||
| ```bash |
Collaborator
There was a problem hiding this comment.
I usually do these things through the GUI (making the release branch/tags/releases), is there a reason the command line version is being recommended instead?
The only thing to note is that the new tag should be made from the release branch and not from main.
Collaborator
Author
There was a problem hiding this comment.
I tend to it via the command line so I can verify I've tagged the correct commit but I agree both methods work.
I've updated the instructions to mention both methods.
b3ec9f3 to
dfd2630
Compare
dfd2630 to
11b5f43
Compare
Co-authored-by: Colm Talbot <talbotcolm@gmail.com>
ColmTalbot
approved these changes
Sep 3, 2025
|
|
||
| If making a major or minor release you must first make the release branch from the current `main` branch | ||
|
|
||
| ```bash |
GregoryAshton
approved these changes
Sep 4, 2025
GregoryAshton
left a comment
Collaborator
There was a problem hiding this comment.
This looks good to me.
mj-will
added a commit
to mj-will/bilby
that referenced
this pull request
Oct 16, 2025
* BLD: use release branch semver * DOC: update `making releases` to describe process using release branches * DOC: fix typo Co-authored-by: Colm Talbot <talbotcolm@gmail.com> * DOC: update docs on making releases --------- Co-authored-by: Colm Talbot <talbotcolm@gmail.com>
mj-will
added a commit
to mj-will/bilby
that referenced
this pull request
Feb 19, 2026
* BLD: use release branch semver * DOC: update `making releases` to describe process using release branches * DOC: fix typo Co-authored-by: Colm Talbot <talbotcolm@gmail.com> * DOC: update docs on making releases --------- Co-authored-by: Colm Talbot <talbotcolm@gmail.com>
isaaclegred
pushed a commit
to isaaclegred/bilby
that referenced
this pull request
Mar 7, 2026
* BLD: use release branch semver * DOC: update `making releases` to describe process using release branches * DOC: fix typo Co-authored-by: Colm Talbot <talbotcolm@gmail.com> * DOC: update docs on making releases --------- Co-authored-by: Colm Talbot <talbotcolm@gmail.com>
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.
Change how we make releases to use release branches.
This should make it easier to backport bug fixes to versions being used in production analyses.
Note: this requires #952