From 3dea0c8c5cdeaa1c9486ac94483f4a0690611f65 Mon Sep 17 00:00:00 2001 From: Paul Menzel Date: Wed, 23 Nov 2016 11:22:18 +0100 Subject: [PATCH] Documentation: Remove *GitHub-Travis CI hints* Although useful, we are not there yet, so remove the paragraph. --- Documenation/SubmittingPatches | 40 ---------------------------------- 1 file changed, 40 deletions(-) diff --git a/Documenation/SubmittingPatches b/Documenation/SubmittingPatches index 69885ae7c..4231d4bc9 100644 --- a/Documenation/SubmittingPatches +++ b/Documenation/SubmittingPatches @@ -116,43 +116,3 @@ branch head. You often want to add additional explanation about the patch, other than the commit message itself. - --------------------------------------------------- -GitHub-Travis CI hints - -With an account at GitHub (you can get one for free to work on open -source projects), you can use Travis CI to test your changes on Linux, -Mac (and hopefully soon Windows). You can find a successful example -test build here: https://travis-ci.org/git/git/builds/120473209 - -Follow these steps for the initial setup: - - (1) Fork https://github.com/git/git to your GitHub account. - You can find detailed instructions how to fork here: - https://help.github.com/articles/fork-a-repo/ - - (2) Open the Travis CI website: https://travis-ci.org - - (3) Press the "Sign in with GitHub" button. - - (4) Grant Travis CI permissions to access your GitHub account. - You can find more information about the required permissions here: - https://docs.travis-ci.com/user/github-oauth-scopes - - (5) Open your Travis CI profile page: https://travis-ci.org/profile - - (6) Enable Travis CI builds for your Git fork. - -After the initial setup, Travis CI will run whenever you push new changes -to your fork of Git on GitHub. You can monitor the test state of all your -branches here: https://travis-ci.org//git/branches - -If a branch did not pass all test cases then it is marked with a red -cross. In that case you can click on the failing Travis CI job and -scroll all the way down in the log. Find the line "<-- Click here to see -detailed test output!" and click on the triangle next to the log line -number to expand the detailed test output. Here is such a failing -example: https://travis-ci.org/git/git/jobs/122676187 - -Fix the problem and push your fix to your Git fork. This will trigger -a new Travis CI build to ensure all tests pass.