Skip to content
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.

Sign up for GitHub

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

Jump to bottom

include safeguards in master branch #783

Open
jsign opened this issue Feb 19, 2021 · 0 comments
Open

include safeguards in master branch #783

jsign opened this issue Feb 19, 2021 · 0 comments

Comments

@jsign
Copy link
Contributor

jsign commented Feb 19, 2021

We highly recommend users avoid running master code, but specific release tags/commit.

We tried some git-flow style of develop as the main development branch, but it has many corner cases that doesn't seem to fit well in Github.

The plan now is to go back to develop on master but:

  • Include in the README big warning about master potentially being unstabled and undocumented.
  • Encourage always to clone specific tags, not branches.
  • Investigate if git-hooks can signal warning messages to notify the user/developer if is in master branch.
  • Change the Makefile to warn the user if it's building or running commands in master.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jsign