Add fixedReleaser to fix BCR app pipeline #1794
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
The GitHub app to automatically publish new releases to the Bazel Central Registry was failing because it was looking for a BCR fork under the user who tags the release. In our case, this is automated by a GitHub action and so there’s no fork. By adding this config file, we override the default releaser to be my username, so the fork https:/balestrapatrick/bazel-central-registry will be correctly found. This behavior is documented here: https:/bazel-contrib/publish-to-bcr/blob/main/templates/README.md#optional-configyml
BalestraPatrick
requested review from
brentleyjones,
keith,
segiddins and
thii
as code owners
thii
approved these changes
Dec 22, 2022
brentleyjones
approved these changes
Dec 22, 2022
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.
The GitHub app to automatically publish new releases to the Bazel Central Registry was failing because it was looking for a BCR fork under the user who tags the release. In our case, this is automated by a GitHub action and so there’s no fork. By adding this config file, we override the default releaser to be my username, so the fork https:/balestrapatrick/bazel-central-registry will be correctly found.
This behavior is documented here: https:/bazel-contrib/publish-to-bcr/blob/main/templates/README.md#optional-configyml