Permalink
Switch branches/tags
Find file Copy path
732606f Apr 4, 2018
4 contributors

Users who have contributed to this file

@sarahhodne @carlad @nschonni @DrTorte
77 lines (57 sloc) 3.3 KB

How to contribute to Travis CI

Found a bug in our code, or have an idea for a feature? Here are some notes on how to best report them so we can get it fixed as quickly as possible.

Security Issues

Any security issues should be submitted directly to security@travis-ci.org

In order to determine whether you are dealing with a security issue, ask yourself these two questions:

  1. Can I access something that's not mine, or something I shouldn't have access to?
  2. Can I disable something for other people?

If the answer to either of those two questions are "yes", then you're probably dealing with a security issue. Note that even if you answer "no" to both questions, you may still be dealing with a security issue, so if you're unsure, just email us at security@travis-ci.org.

Build Failures

Please note that our issue tracker's main purpose is to track bugs for Travis CI. If your build is passing locally, but not on Travis CI, please make sure that it's an issue with Travis before reporting it.

Some frequent reasons for builds failing on Travis CI:

  • 3rd party dependencies missing
  • Minor differences between OS X and Linux (such as whether the filesystem is case-sensitive or not).

A good place to ask for advice when your build is failing on Travis CI is the travis-ci tag on Stack Overflow.

Other Issues

Found a bug in Travis CI? Here are some notes on how to report the bug so we can fix it as fast as possible:

  • Explain, as detailed as possible, how to reproduce the issue.
  • Include what you expected to happen, as well as what actually happened.
  • If it's a bug with the website, please include information on what browser version and operating system you are running.
  • If it helps, feel free to attach a screenshot or video illustrating the issue.
  • If you're having trouble with a specific build, please include a link to the build or job in question.
  • Include all this information in a new issue on our Issue Tracker

Pull Requests

Know how to fix something? We love pull requests! Here's a quick guide:

  1. Check for open issues, or open a fresh issue to start a discussion around a feature idea or a bug. Opening a separate issue to discuss the change is less important for smaller changes, as the discussion can be done in the pull request.
  2. Fork the relevant repository on GitHub, and start making your changes.
  3. Check out the README for the project for information specific to that repository.
  4. Push the change (we recommend using a separate branch for your feature).
  5. Open a pull request.
  6. We try to merge and deploy changes as soon as possible, or at least leave some feedback, but if you haven't heard back from us after a couple of days, feel free to leave a comment on the pull request.

Automatic closure of old issues

If an issue has been left open and untouched for 90 days or more, we automatically close them. We do this to ensure that new issues are more easily noticeable, and that old issues that have been resolved or are no longer relevant are closed. You can read more about this here.