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.

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 branching strategy #334

Open
nefarius opened this issue Feb 18, 2024 · 0 comments
Open

Change branching strategy #334

nefarius opened this issue Feb 18, 2024 · 0 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@nefarius
Copy link
Owner

This is one of the few projects that sadly do not yet cohere to Git best practices, so the master branch is messy and not suited to guarantee producing working builds. After getting the v3 features done, change branching strategy to:

  • master - always builds without errors and can produce a working copy, however might miss latest features
  • develop - main "unstable" branch where all the work is done in

Also start using branches and PRs more, this has the nice side effect of GitHub being able to auto-generate proper changelogs.

@nefarius nefarius added documentation Improvements or additions to documentation enhancement New feature or request labels Feb 18, 2024
@nefarius nefarius self-assigned this Feb 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant