Merged
Conversation
Member
|
Are we dropping the guidance to merge to |
Contributor
Author
|
@martincostello sorry. i completely forgot about that convention. yes my preference would be to move to a "direct to main branch" model. |
Member
|
I’m happy with that if @joelhulen’s cool with it - it’s less effort 😆 As long as we’re all doing the same thing so we don’t end up with two different branches and a merge headache later. |
Member
|
@SimonCropp and @martincostello, I'm cool with that change. It's less confusing and less effort this way. |
Closed
martincostello
approved these changes
Dec 16, 2022
This was referenced Sep 29, 2025
This was referenced Jan 16, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.