-
Notifications
You must be signed in to change notification settings - Fork 287
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
config file for rustc-apfloat crate #1029
config file for rustc-apfloat crate #1029
Conversation
…dyb and wesley are providing.
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.
Moved the repo over.
repos/rust-lang/rustc-apfloat.toml
Outdated
# the least-privileged access for the short term, solely to placate the CI. | ||
[access.teams] | ||
compiler = 'read' | ||
compiler-contributors = 'read' |
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.
We don't currently support read access (which is why CI is failing). I might instead create a rustc_apfloat subgroup under compiler and use that here.
Co-authored-by: Wesley Wiser <wwiser@gmail.com>
sweet https://github.com/rust-lang/rustc_apfloat has been transferred, which I think means we can move forward with merging this. |
eddyb will be transferring their factored out rustc-apfloat crate, https://github.com/LykenSol/rustc_apfloat, into the rust-lang/ organization (see rust-lang/rust#55993 for background).
This is an initial team configuration for us to get the crate up and running under rust-lang/ organization.
However, eddyb has expressed an explicit wish for the source code to be transferred (i.e. moved, not copied, ha ha), in order to ensure that e.g. stray links to the old repository are handled properly within github.
So, the process I'm planning here is: