Skip to content
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

Add a seperate rust-try repo and corresponding automation #14978

Closed
brson opened this issue Jun 17, 2014 · 2 comments
Closed

Add a seperate rust-try repo and corresponding automation #14978

brson opened this issue Jun 17, 2014 · 2 comments

Comments

@brson
Copy link
Contributor

brson commented Jun 17, 2014

We've about outgrown the phase where I'm comfortable with people just pushing to the main repo to do test runs, and try pushes are one of the main reasons we have to give people write access via the 'Rust-Push' group. Let's move this functionality to it's own repo, and possibly even to it's own automation infrastructure.

@nikomatsakis
Copy link
Contributor

On Tue, Jun 17, 2014 at 11:55:40AM -0700, Brian Anderson wrote:

We've about outgrown the phase where I'm comfortable with people
just pushing to the main repo to do test runs, and try pushes are
one of the main reasons we have to give people write access via the
'Rust-Push' group. Let's move this functionality to it's own repo,
and possibly even to it's own automation infrastructure.

It would also be useful to have try runs test a superset of what bors
tests -- or at least have the option to do so.

@steveklabnik
Copy link
Member

Becuase of the way GitHub works, we can't really remove push permissions. As such I'm giving this a close, sad as it is.

(it'd be awesome if only @bors had push ability)

bors added a commit to rust-lang-ci/rust that referenced this issue Jun 5, 2023
Emit `'_` for lifetime generics in `HirDisplay`

This makes the generated code not linted by `rust_2018_idioms` lint. But that is an allow by default lint, so should we do this? Maybe we should only do this for `DisplayTarget::SourceCode`?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants