Re: [RFC/PATCH v1] Add Travis CI support
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Sep 25, 2015, 07:27 UTC
- Message-ID
- <699c08632232180166145f70c7f16645@dscho.org>
- In-Reply-To
- <1443150875.3042.3.camel@kaarsemaker.net>
Hi,
On 2015-09-25 05:14, Dennis Kaarsemaker wrote:
Show 14 quoted lines
> On do, 2015-09-24 at 17:41 -0700, Junio C Hamano wrote: >> larsxschneider@gmail.com writes: >> >> > My idea is that the owner of "https://github.com/git/git" enables this account >> > for Travis (it's free!). Then we would automatically get the test state for all >> > official branches. >> >> The last time I heard about this "it's free" thing, I thought I >> heard that it wants write access to the repository. > > It does not need write access to the git data, only to auxiliary GitHub > data: commit status and deployment status (where it can put "this > commit failed tests"), repository hooks (to set up build triggers), > team membership (ro) and email addresses (ro).
If that still elicits concerns, a fork could be set up that is automatically kept up-to-date via a web hook, and enable Travis CI there.
Junio, if that is something with which you feel more comfortable, I would be willing to set it up. Even if the visibility (read: impact) would be higher if the badges were attached to https://github.com/git/git proper...
Ciao, Dscho