-
Notifications
You must be signed in to change notification settings - Fork 20
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
File issues automatically #6
Comments
It might also file a rust issue, depending on whose responsibility we feel it is to fix. I lean towards it probably being the PR author's job to fix, so that might make rust-lang/rust be the natural repository. |
bors
added a commit
to rust-lang/rust
that referenced
this issue
Feb 12, 2019
Automatically open an issue when a tool breaks cc @nikomatsakis fixes rust-lang-nursery/rust-toolstate#6 documentation about issue opening via the github api: https://developer.github.com/v3/issues/#create-an-issue
bors
added a commit
to rust-lang/rust
that referenced
this issue
Feb 13, 2019
Automatically open an issue when a tool breaks cc @nikomatsakis fixes rust-lang-nursery/rust-toolstate#6 documentation about issue opening via the github api: https://developer.github.com/v3/issues/#create-an-issue
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my ideal world, when toolstate detects breakage in a tool, it would file an issue in the relevant tool, cc'ing all the parties involved... thoughts?
The text was updated successfully, but these errors were encountered: