Give the Rustup team access to rustup-components-history - #2758
Merged
Merged
Conversation
2 tasks
Dry-run check results |
Contributor
|
@Kobzol should we make the most of this PR and eventually add simple branch protection for this repo? |
Member
Author
|
Yeah, good point, I was thinking the same. While at it, I also switched GH pages to the modern workflow mechanism, I will switch the GH pages workflow to use it. |
ubiratansoares
approved these changes
Sep 16, 2026
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
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.
Suggested here.
Since the repo has a lot to do with Rustup, I think that the team should have access.
CC @rust-lang/rustup