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

Get rid of the master/incoming distinction #6024

Closed
bstrie opened this issue Apr 23, 2013 · 4 comments
Closed

Get rid of the master/incoming distinction #6024

bstrie opened this issue Apr 23, 2013 · 4 comments

Comments

@bstrie
Copy link
Contributor

bstrie commented Apr 23, 2013

In theory, Bors should be keeping the incoming branch green at all times. Is this distinction still necessary?

Pros to getting rid of the distinction:

  • Online docs only get built from master, so this keeps docs and development in sync
  • There's no longer any need to tell people to target PRs at incoming
  • No more questions regarding the difference between incoming and master

Cons:

  • Sometimes incoming is still red despite Bors
@brendanzab
Copy link
Member

This would be handy for library writers too.

@bstrie
Copy link
Contributor Author

bstrie commented May 9, 2013

Nominating for 0.7.

@graydon
Copy link
Contributor

graydon commented May 16, 2013

just a bug, removing milestone/nomination.

@bstrie
Copy link
Contributor Author

bstrie commented Jun 27, 2013

Done, closing.

@bstrie bstrie closed this as completed Jun 27, 2013
flip1995 pushed a commit to flip1995/rust that referenced this issue Sep 10, 2020
print the unit type `()` in related lint messages.

changelog: print the unit type `()` in related lint messages
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