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

Dropping the development branch and renaming master to main #397

Open
marcelluethi opened this issue Feb 27, 2023 · 2 comments
Open

Dropping the development branch and renaming master to main #397

marcelluethi opened this issue Feb 27, 2023 · 2 comments
Assignees

Comments

@marcelluethi
Copy link
Contributor

When we started development of scalismo and scalismo-ui, we decided to follow the git-flow branching model. The main feature is to have a separate development branch.

I would argue that at this point, this model is over-complicated and no longer needed. Instead I would propose to base development on the master branch. Furthermore, I propose to rename master to main, as this is the new standard everywhere.

@Andreas-Forster You were also involved from the beginning. Do you see any reasons to keep the development branch?

@Andreas-Forster
Copy link
Member

As it is currently evolving, I do not see any reason not to change it. Currently, it really seems to better fit our needs.

@madsendennis
Copy link
Collaborator

madsendennis commented Mar 21, 2024

This issue already seems to be semi-implemented.
master has already been renamed to main.
Still to be done:

  • Remove develop branch
  • Update workflow to trigger on main instead of master and not on develop.

Anything else missing and preventing this issue from being closed?

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

No branches or pull requests

3 participants