From 61bd2ae94b218feadf751de56beaaa19b52f1b28 Mon Sep 17 00:00:00 2001 From: daira <> Date: Mon, 2 Sep 2013 19:44:31 +0000 Subject: [PATCH] note Travis permission issue [Imported from Trac: page NewbieDeveloperSetup, version 15] --- NewbieDeveloperSetup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/NewbieDeveloperSetup.md b/NewbieDeveloperSetup.md index a39afe1..adbdf62 100644 --- a/NewbieDeveloperSetup.md +++ b/NewbieDeveloperSetup.md @@ -8,7 +8,7 @@ As I'm progressing my first steps in hacking tahoe-lafs I thought it might help I will use Eclipse IDE because of wide use and availability. But just because I'm used to it. You might have your preferred tools. I'm on Ubuntu. -The easiest workflow you can use is by working using Github's [Pull Requests](https://help.github.com/articles/using-pull-requests). Tahoe-LAFS's code has automated test coverage and each PR you will send will be tested automatically. However, if you want tests to be run even before sending a PR, [set up Travis CI on your own [GitHub](GitHub) forked repo](http://about.travis-ci.org/docs/user/getting-started/). This way, each commit you'll make, will have tests run on it. +The easiest workflow you can use is by working using Github's [Pull Requests](https://help.github.com/articles/using-pull-requests). Tahoe-LAFS's code has automated test coverage and each PR you will send will be tested automatically. However, if you want tests to be run even before sending a PR, and if you're prepared to accept the [security issue of Travis needing write access](https://github.com/travis-ci/travis-ci/issues/1390), see [these docs for how to set up Travis CI on your own [GitHub](GitHub) forked repo](http://about.travis-ci.org/docs/user/getting-started/). This way, each commit you'll make, will have tests run on it. 1. Set up your OS. (I tinker a lot with mine so I maybe miss some). You have to [install python in your OS](http://python.org/download/) for tahoe to run. Most Linux distributions have it in their software repositories.