[bazel] Setup workflow to publish to BCR#1639
[bazel] Setup workflow to publish to BCR#1639mmorel-35 wants to merge 2 commits intoemscripten-core:mainfrom
Conversation
mmorel-35
force-pushed
the
bcr
branch
2 times, most recently
from
f63d8bd to
e0ae060
Compare
sbc100
changed the title
sbc100
left a comment
sbc100
left a comment
There was a problem hiding this comment.
I don't know much about this stuff I'm afraid. Perhaps @walkingeyerobot can review?
|
The workflow is provided based on https://github.com/bazel-contrib/publish-to-bcr/ and BCR is here |
Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
| attestations: write | ||
| secrets: | ||
| # Necessary to push to the BCR fork, and to open a pull request against a registry | ||
| publish_token: ${{ secrets.BCR_PUBLISH_TOKEN }} |
There was a problem hiding this comment.
You'll need to create a dedicated token
There was a problem hiding this comment.
Can you tell me the exact steps I need to take here?
There was a problem hiding this comment.
There was a problem hiding this comment.
Can you use ${{ secrets.EMSCRIPTEN_BOT_TOKEN }} here? Then I will give the bot the ability to create PRs in https://github.com/emscripten-core/bazel-central-registry
Will that work?
Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
|
|
||
| fixedReleaser: | ||
| login: sbc100 | ||
| email: sbc@chromium.org |
There was a problem hiding this comment.
@kripken do we have some other email we can use here other than my (or your) personal one?
| @@ -0,0 +1,23 @@ | |||
| name: Publish to BCR | |||
There was a problem hiding this comment.
Can you replace "BCR" with something like "Bazel Registry" ? Both in the name of this file and in the name field here?
The "bcr" acronym won't mean anything folks who don't work with bazel.
|
What do we need to do to move this forward? |
2 participants
This provide the workflow to publish each new tag to the BCR as it was yet done https://github.com/bazelbuild/bazel-central-registry/tree/main/modules/emsdk
Fixes: #1674