Add BCR workflow for Bazel Central Registry publishing #340
+230
−0
Conversation
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
Author
|
/cc @BYVoid |
Member
|
As such, this will not work, of course. |
Author
|
That's based on @BYVoid work in BCR. Can you provide some guidance to make this work ? |
mmorel-35
force-pushed
the
bcr
branch
2 times, most recently
from
2351ab7 to
eba6e93
Compare
Member
This will not work because your configuration requires a secret token: |
Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
mmorel-35
commented
Dec 6, 2025
Comment on lines
+52
to
+77
| ### Creating a Personal Access Token | ||
|
|
||
| 1. **Navigate to GitHub Settings** | ||
| - Go to https://github.com/settings/tokens | ||
| - Or: Click your profile picture → Settings → Developer settings → Personal access tokens → Tokens (classic) | ||
|
|
||
| 2. **Generate New Token** | ||
| - Click "Generate new token (classic)" | ||
| - Give it a descriptive name, e.g., "BCR Publishing for fast_float" | ||
| - Set an appropriate expiration (recommended: 1 year with calendar reminder to renew) | ||
|
|
||
| 3. **Select Required Scopes** | ||
| - ✅ **`repo`** (Full control of private repositories) - Required for accessing repository details | ||
| - ✅ **`workflow`** (Update GitHub Action workflows) - Required for the publishing action | ||
|
|
||
| 4. **Generate and Copy** | ||
| - Click "Generate token" at the bottom | ||
| - **Important**: Copy the token immediately - you won't be able to see it again! | ||
|
|
||
| 5. **Add as Repository Secret** | ||
| - Go to the fast_float repository settings | ||
| - Navigate to: Settings → Secrets and variables → Actions | ||
| - Click "New repository secret" | ||
| - Name: `BCR_PUBLISH_TOKEN` | ||
| - Value: Paste the token you copied | ||
| - Click "Add secret" |
Author
There was a problem hiding this comment.
I'm not allowed to provide the token, this is a task for fast_float project maintainer, see this
Member
|
@LeszekSwirski can you review this ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
Provide the workflow to publish the new versions of the Bazel module
Based on https://github.com/bazelbuild/bazel-central-registry/tree/main/modules/fast_float
https://github.com/bazel-contrib/publish-to-bcr/tree/main?tab=readme-ov-file#setup