README: Renamed default branch #808
Merged
Conversation
This file contains 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
|
Can you also adjust the GitHub actions, please? No build is triggered when merging, currently. |
|
No build is triggered for pull requests, either. Really, this is all going in the wrong order 😞 |
|
I'm going to go ahead and merge this. Then we can tackle the rest later. |
|
Sorry I was away from a big screen, hope things turn out OK! |
|
Yes, everything seems to work now, thanks! |
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.
Summary
This is a start of "get the default branch name" used everywhere.
Details
A name change was started, this keeps it going.
Motivation and Context
It was mentioned in cucumber/common#1507
How Has This Been Tested?
Not tested yet!
I searched, and found more places than this, but this is a start.
Types of changes
Checklist: