-
Notifications
You must be signed in to change notification settings - Fork 0
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
Chaotic repo branching structure #68
Comments
Given this repo has now been running for a while with @w-le if this happens, can you comment on high tightly any other tooling may be using specific branch names vs just pulling the default? Is it safe to rename this to properly reflect their current usage? |
@w-le bump. |
yep agreed, I can confirm that downstream automation is just using the default branch (which is currently beta) so it would be fine and safe to delete https://gitlab.com/aca-engine/deploy/o365-engine/-/blob/master/Dockerfile#L26 |
Closing with |
Over the past 12 - 18 months the branching structure has devolved into an overly complex mix of long-running feature branches and a neglected
master
/beta
release channel. Some housekeeping is currently in place to correct and simplify this.Changes will be communicated here as they are enacted.
Please be advised that there will be some volatility and high PR churn while this takes place. If you are dis-interested it may be a good idea to mute notifications for a little while.
The text was updated successfully, but these errors were encountered: