-
Notifications
You must be signed in to change notification settings - Fork 126
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
Change default repository #22
Comments
Good point. +1 |
👍 |
The default repo can be changed easily if all members aggree: https://help.github.com/articles/setting-the-default-branch/ |
Since no one objected to the issue I have now changed the default branch to "dev". |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
You discussed your git workflow on your release meeting and semi-decided in favor of the common git-flow. This flow changes the meaning of the master branch from a "main"-branch to a "latest-release"-branch that is relatively outdated. Yet, it is the first branch that you visit on your git-hub.
It might be useful if you change the default branch from master to develop.
The text was updated successfully, but these errors were encountered: