-
Notifications
You must be signed in to change notification settings - Fork 317
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to configure this with gitflow? #175
Comments
Change your default branch to master? Or perhaps we should provide a way to override the default branch. |
That would mean all the PRs point at master by default and checking out the repo across team members starts from master. Kind of defeats the purposes of gitflow I think |
We would need the ability to set the release branch separate from the github default branch in order for us to use it. |
Can you walk me through the issue you're having in a little more detail? I can see that you used the |
Hey we have the same issue here - we follow gitflow and would prefer that all draft releases are created on the master branch, rather than default develop branch (as is common under gitflow). Just to elaborate on the issue:
|
This is indeed the same problem I am encountering |
In our gitflow-like scenario we have A problem we have (that sounds similar to the issue description) happens in the following scenario: 1 - A release branch gets created, testing starts and could take several days The actual problem that happened in the meanwhile: the PRs that get merged in step 2 do not appear in the next release draft. |
I think the problems you are facing can be solved with the |
You also might be interested in #1061 |
I tried, really. But I didn't find a way to create the release.
Our repo has base branch set to develop, but I only want to create releases for code ending up on master.
Relevant Release Drafter config: https://github.com/inthepocket/hubble-scripts/blob/develop/.github/release-drafter.yml
Tried first with merging remotes into master and pushing, then tried to merge via PR from develop to master, but the release is not showing up as a Draft when I go to the releases tab.
The text was updated successfully, but these errors were encountered: