-
Notifications
You must be signed in to change notification settings - Fork 32
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Don't assume we are on the
main
branch when collecting release notes
- Loading branch information
Showing
2 changed files
with
6 additions
and
1 deletion.
There are no files selected for viewing
This file contains 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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,5 @@ | ||
--- | ||
encoding: utf8 | ||
default_branch: main | ||
unreleased_version_title: "Upcoming release (``main`` branch)" | ||
unreleased_version_title: "Upcoming release" | ||
earliest_version: 0.1.0 |
70434d6
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.
I accidentally pushed this to
main
instead of making a PR. I thought the branch protection rule would prevent this, but I guess it allows it since I am a repository admin (:joy:).Since we build our docs from a stable branch now, the goal here is for them to say the name of the correct stable branch instead of
main
in the release notes. I want to start maintaining the stable backports at some point (probably after the 0.3 release), and it will be better to have this correctly labeled by then.