We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Figure out a branching strategy and document it
The text was updated successfully, but these errors were encountered:
develop represents current development, "unstable", default branch on GitHub. All PRs to/from this
develop
master represents "stable". On release, commits are merged from develop into master, and tagged (useful for #12 )
master
master represents current development, "unstable", default branch on GitHub. All PRs to/from this.
Releases are tracked as tags. To checkout, simply checkout by specific tag.
Personally I prefer the latter, as it removes the need for an extra branch.
Sorry, something went wrong.
Suggestion 1 mirrors how Home Assistant does this.
It might be a plan to avoid the master branch name controversy and rename it to stable.
i like 1 and also think we should use stable vs master...
No branches or pull requests
Figure out a branching strategy and document it
The text was updated successfully, but these errors were encountered: