Terminology update 'master' to 'main' in DEVELOPING.md#502
Merged
thundergolfer merged 2 commits intomainfrom Jul 8, 2021
Merged
Terminology update 'master' to 'main' in DEVELOPING.md#502thundergolfer merged 2 commits intomainfrom
thundergolfer merged 2 commits intomainfrom
Conversation
Author
|
Requesting @hrfuller as I think Alex may be on vacation. |
Author
|
:bump: @hrfuller Merging this should also trigger CI and we can check it's compatible with our new |
alexeagle
approved these changes
Jul 8, 2021
Author
|
@philwo our scheduled builds are failing due the |
Contributor
|
@fweikert has an open PR for this already on bazelbuild/continuous-integration repo |
Author
|
Is there? I can't see it https://github.com/bazelbuild/continuous-integration/issues?q=is%3Aissue+author%3Afweikert+ |
Contributor
Author
|
@philwo Thanks mate 🙏 |
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.


Change directly related to #500
As far as I can see these are the only relevant
masterrefs in the codebase.PR Checklist
Please check if your PR fulfills the following requirements:
.parfiles. See CONTRIBUTING.md for infoPR Type
What kind of change does this PR introduce?
Does this PR introduce a breaking change?