Skip to content

Conversation

@fregante
Copy link
Member

@fregante fregante commented May 30, 2017

Related to #103

It's hard to show the branch in the PR list, but it's easy in the PR itself.

base branch highlight

@busches
Copy link
Member

busches commented May 30, 2017

What about repos utilizing something like GitFlow that actively merge into develop or another non-master branch? Almost all of the PRs will be flagged.

@fregante
Copy link
Member Author

What's the base/default branch in that case? I mean the one marked under /settings/branches

@smeijer
Copy link
Contributor

smeijer commented May 31, 2017

@bfred-it , usually develop. You create a feature branch from develop, add your changes and submit a PR back to develop. master is only used to manage releases.

At the moment of release, develop is merged into master, and master is deployed to production. The master branch always contains the version as it is running in production.

Only hotfixes that should be deployed to production ASAP, and cannot wait for a normal release cycle, are being branched from master, and merged back to both master and develop.

@fregante fregante closed this May 31, 2017
@fregante fregante deleted the highlight-non-master-branch branch May 31, 2017 07:26
@fregante
Copy link
Member Author

It'll need an HTTP request then

@jgierer12
Copy link
Contributor

I also know of a few repos that have gh-pages as the default branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

4 participants