1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
NO CARRIER
======
[](https://travis-ci.org/twbs/no-carrier)
[](https://github.com/twbs/no-carrier/blob/master/LICENSE.txt)
NO CARRIER is a tool to auto-close old GitHub issues and pull requests that were abandoned by their reporter, which is to say that we were waiting for a response from the reporter but never got a response in a reasonable amount of time.
Named after [the message indicating that your dial-up modem has lost its connection.](http://en.wikipedia.org/wiki/NO_CARRIER#As_Internet_slang)
## Motivation
You're a member of a popular open source project. Cool.
But due to the project's popularity, you get lots of bug reports on the issue tracker, and often these reports are lacking key information that's explicitly mentioned in your bug reporting docs as being required. Or maybe you just need extra information or test results from the bug reporter. So, okay, you post nice reply comments on the issues, asking the reporters for the information or requesting that they do some investigation/tests.
And then you wait for a reply. Unfortunately, for whatever reason, a surprisingly large fraction of folks never end up replying to your questions/requests. So unactionable issues start to pile up. You occasionally review the oldest batch of such issues and close them manually.
By automating the process of closing abandoned issues, the issue tracker is kept clean with less tedium on the part of issue triagers. The abandoned issue expiration policy is also applied more uniformly/fairly, and it's easier to use a canonical template for the closing issue comment that clearly and politely explains the reason for the closure.
Example of the bot in action:
## Used by
* [Bootstrap](https://github.com/twbs/bootstrap); see [@twbs-closer](https://github.com/twbs-closer)
* [Your Project Here]; send us a pull request and we'll add you to the list
## Usage
NO CARRIER is designed to be run as a [cron job](https://en.wikipedia.org/wiki/Cron).
Java 8+ is required to run NO CARRIER. You can download NO CARRIER's prebuilt assembly JAR from [our GitHub Releases page](https://github.com/twbs/no-carrier/releases). For instructions on building NO CARRIER yourself from source, see [the Contributing docs](https://github.com/twbs/no-carrier/blob/master/CONTRIBUTING.md).
NO CARRIER requires 2 environment variables to be set:
* `$GITHUB_USERNAME` - Username of GitHub user for NO CARRIER to login as
* `$GITHUB_PASSWORD` - Password of GitHub user for NO CARRIER to login as
NO CARRIER accepts exactly 3 command line arguments. Once you have the JAR, run e.g. `java -jar no-carrier.jar <owner/repo> <label> <days>`. Here's what each of the arguments is:
* `owner/repo`: GitHub repo whose issues will be operated upon (example: `twbs/bootstrap` for [Bootstrap](https://github.com/twbs/bootstrap))
* `label`: Name of label used on the repo's GitHub issue tracker to indicate that the issue is blocked waiting for a reply from a user (typically the issue's original poster).
* `days`: Integer number of days. If at least this number of days elapses after an issue has been labeled without any new comment being posted, NO CARRIER will close the issue and post an explanatory comment.
### Heroku
We also have specific [instructions for setting up NO CARRIER on Heroku](https://github.com/twbs/no-carrier/wiki/Heroku), courtesy of [@zxqfox](https://github.com/zxqfox).
### Pull requests
NO CARRIER closes old pull requests according to the same rules it uses to close old issues. This is possible since GitHub treats issues and pull requests as different variations of the same underlying object.
## License
NO CARRIER is released under the [MIT License](https://github.com/twbs/no-carrier/blob/master/LICENSE.txt).
## Acknowledgments
We all stand on the shoulders of giants and get by with a little help from our friends. NO CARRIER is written in [Scala](http://www.scala-lang.org) and built on top of:
* [jcabi-github](https://github.com/jcabi/jcabi-github), for working with [the GitHub API](https://developer.github.com/v3/)
* [Logback](http://logback.qos.ch/) and [Scala Logging](https://github.com/typesafehub/scala-logging), for logging (duh)
* [specs2](http://etorreborre.github.io/specs2/) for unit tests
## See also
* [LMVTFY](https://github.com/cvrebert/lmvtfy), NO CARRIER's sister bot who does HTML validation
* [Savage](https://github.com/twbs/savage), NO CARRIER's sister bot who runs cross-browser JS tests on Sauce Labs
* [Rorschach](https://github.com/twbs/rorschach), NO CARRIER's sister bot who sanity-checks Bootstrap pull requests
* The previous incarnation of [@rails-bot](https://github.com/rails-bot), which [warned about inactive issues](https://github.com/rails/rails/issues/20733#issuecomment-166952376)
|
