-
Notifications
You must be signed in to change notification settings - Fork 301
Backport rust-analyzer repos (batch 2) #1807
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
base: master
Are you sure you want to change the base?
Conversation
org = "rust-analyzer" | ||
name = "rustc-auto-publish" | ||
description = "" | ||
bots = [] | ||
|
||
[access.teams] | ||
rust-analyzer = "write" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With this I will lose access to the repo settings is that correct? Cause right now I kind of need access for managing the crates-io token there for publishing (whenever we need to publish-new something as the current token only has publish-update permissions)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I changed it to "maintain", but I'm not sure if that will be enough. If not, we can discuss how to proceed with t-infra, because we'd like to avoid giving admin permissions, as these allow destroying repos or transferring them out of the org.
Dry-run check results
|
Backporting the following repos:
countme
Original content
metrics
Original content
rust-analyzer.github.io
Original content
rustc-auto-publish
Original content
#t-compiler/rust-analyzer > Rust-analyzer org repository access and status @ 💬
CC @rust-lang/rust-analyzer