Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Sign up
Appearance settings

Add BCR workflow for Bazel Central Registry publishing #340

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mmorel-35 wants to merge 1 commit into fastfloat:main
base: main
Choose a base branch
Loading
from mmorel-35:bcr

Conversation

@mmorel-35
Copy link

@mmorel-35 mmorel-35 commented Dec 3, 2025 •
edited
Loading

Copy link
Author

/cc @BYVoid

Copy link
Member

lemire commented Dec 4, 2025

As such, this will not work, of course.

Copy link
Author

mmorel-35 commented Dec 6, 2025 •
edited
Loading

That's based on @BYVoid work in BCR.

Can you provide some guidance to make this work ?

@mmorel-35 mmorel-35 force-pushed the bcr branch 2 times, most recently from 2351ab7 to eba6e93 Compare December 6, 2025 11:10
Copy link
Member

lemire commented Dec 6, 2025

@mmorel-35

That's based on @BYVoid work in BCR. Can you provide some guidance to make this work ?

This will not work because your configuration requires a secret token: BCR_PUBLISH_TOKEN. If you have this secret token, you can communicate with me privately and share it with me, and I can add it to the repo.

 

Signed-off-by: Matthieu MOREL <matthieu.morel35@gmail.com>
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"
Copy link
Author

@mmorel-35 mmorel-35 Dec 6, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm not allowed to provide the token, this is a task for fast_float project maintainer, see this

Copy link
Member

lemire commented Dec 6, 2025

@LeszekSwirski can you review this ?

Copy link
Member

lemire commented Dec 29, 2025

Note that I am holding this because I don't know anything about the bazel central registry, so I cannot review. Help needed.

Copy link
Contributor

BYVoid commented Jan 13, 2026

I don't own the bcr repository. But let me see how the bcr token works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

1 more reviewer

@BYVoid BYVoid BYVoid approved these changes

Reviewers whose approvals may not affect merge requirements

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

AltStyle によって変換されたページ (->オリジナル) /