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

Clean up branches #58

Open
2 tasks
DieterHolvoet opened this issue Oct 28, 2021 · 3 comments
Open
2 tasks

Clean up branches #58

DieterHolvoet opened this issue Oct 28, 2021 · 3 comments

Comments

@DieterHolvoet
Copy link
Contributor

Description

  • Clean up unused branches (check Sourcegraph to make sure the branch is not directly required in a composer.json file)
  • Switch default branch to main
@RobinHoutevelts
Copy link
Contributor

Only feature/split is currently being used in some of our projects. But as I understand it, the split-pre is needed for a smooth upgrade?

These are all current branches:

  • release/v0.6
  • feature/split
  • feature/split-pre

@DieterHolvoet
Copy link
Contributor Author

Yes, those split branches will be needed for the upgrade. It's all documented here. We should finish that upgrade some time soon, it's basically finished anyway.

release/v0.6 is a branch for a certain version, so we probably shouldn't delete that one. The default branch is switched to main, so I think this issue is okay now.

@DieterHolvoet
Copy link
Contributor Author

The feature/split and feature/split-pre branches can be deleted if they are not required anymore in any of your projects. I won't delete them.

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
2 participants
@DieterHolvoet @RobinHoutevelts