GitHub Community
Releases "XXX commits to master since this release" must be a configurable branch #68862
Unanswered
marekr
asked this question in
Repositories
Replies: 1 comment 1 reply
-
|
They completely removed it 😢 That's terrible, this was one of the most useful infos here in the releases page for maintainers!! Even the default branch already helped here.. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
See https://github.com/orgs/community/discussions/201116 |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Product Feedback
Body
The inability to configure the "base branch" for a release, makes this statement
nonsensical.
In our workflow, our releases are on a "stable" branch and the tags are made there, the master branch is indeed 3000 commits later and is considered the unstable branch until a release 1 year later. We make the unstable branch our default because that is indeed our development head and the stable is purely bug fixing.
It would be great if this was configurable on Releases.
Beta Was this translation helpful? Give feedback.
All reactions