@@ -289,7 +289,6 @@ An example submission could now look as follows:
289289 Bug fix: no
290290 Feature addition: yes
291291 Backwards compatibility break: no
292- Symfony2 tests pass: yes
293292 Fixes the following tickets: #12, #43
294293 Todo: -
295294 License of the code: MIT
@@ -347,17 +346,6 @@ When you save, git will start rebasing, and if successful, will ask you to
347346edit the commit message, which by default is a listing of the commit messages
348347of all the commits. When you finish, execute the push command.
349348
350- ..tip ::
351-
352- To automatically get your feature branch tested, you can add your fork to
353- `travis-ci.org `_. Just login using your github.com account and then simply
354- flip a single switch to enable automated testing. In your pull request,
355- instead of specifying "*Symfony2 tests pass: [yes|no] *", you can link to
356- the `travis-ci.org status icon `_. For more details, see the
357- `travis-ci.org Getting Started Guide `_. This could easily be done by clicking
358- on the wrench icon on the build page of Travis. First select your feature
359- branch and then copy the markdown to your PR description.
360-
361349.. _ProGit :http://git-scm.com/book
362350.. _GitHub :https://github.com/signup/free
363351.. _`Github's Documentation` :https://help.github.com/articles/ignoring-files