Skip to content

travis-ci/docs-travis-ci-com

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ac04d49 · Dec 2, 2024
Jul 11, 2018
Jan 12, 2023
Dec 2, 2024
Oct 16, 2024
May 28, 2017
Nov 4, 2024
Feb 18, 2020
Aug 6, 2024
Aug 9, 2021
Oct 16, 2024
Aug 5, 2024
Jan 8, 2019
Dec 2, 2024
Nov 9, 2016
Nov 9, 2016
Apr 15, 2020
May 5, 2020
Nov 30, 2017
Nov 30, 2017
Jul 8, 2019
Sep 11, 2024
Aug 5, 2024
Jan 16, 2014
Apr 2, 2018
Jan 16, 2024
Jul 1, 2020
Nov 4, 2024
Nov 20, 2015
Oct 8, 2024
May 5, 2020
Oct 21, 2024
Oct 16, 2018
May 1, 2018
May 28, 2017
Mar 3, 2015
Sep 25, 2018
Apr 13, 2022
Oct 16, 2024

Repository files navigation

About Travis CI Repository Build Status

This is the documentation site for Travis CI!. Follow this guide to learn how to add new documentation and how to update existing documentation.

Add Documentation

The following are the steps to add documentation.

  1. Review the Travis CI documentation guidelines.
  2. Check existing documentation. Verify that the documentation does not already exist or look for related documentation that can be enhanced.
  3. Determine proper placement. In the Travis CI repository, browse to the user folder (or any other specific folder) and create a new branch.
  4. Create a new file and add the new documentation files.
  5. Ensure to insert the name and extension for the file.
  6. Commit your changes and add a short message to describe your changes.
  7. Test the changes locally to verify your edits.
  8. Submit a pull request. Include a clear title and description of the proposed changes, and click “Create pull request.”

Thank you for your contribution! The Travis CI team will review the pull request and approve any necessary changes.

Update Existing Documentation

If you see a page that needs to be updated or that can be improved, follow these steps to update Travis CI's existing documentation.

  1. Review the Travis CI documentation guidelines.
  2. Identify the Travis CI docs page that needs to be updated.
  3. Click the “Improve this page on GitHub” button in the top right corner.
  4. Once on GitHub, edit the relevant file.
  5. Commit your changes. Name your branch, and click the “Propose changes” button.
  6. Build the docs in a local environment to verify your edits.
  7. Submit a pull request. Ensure a clear title and description of the proposed changes are added, and click “Create pull request.”

Thank you for your contribution. The Travis CI team will review the pull request and approve any necessary changes.

Build Local Environment

You can inspect how the documentation site will reflect your edits. Follow the steps below to learn how to build your local environment and check all your edits before sending the pull request for approval.

Install Dependencies

Follow the steps below to install dependencies.

  1. Ensure you have Ruby and RubyGems installed.

  2. Clone the Travis CI docs repository.

  3. Install bundler as follows:

    $ gem install bundler
  4. Next, install application dependencies:

    $ bundle install --binstubs

Generate Documentation

To generate the documentation, run the following command:

$ ./bin/jekyll build

Run the Application Server

You are ready to start your local documentation site using Jekyll or Puma. For documentation edits, Jekyll is sufficient.

Edit with Jekyll

To start and inspect your edits using Jekyll, follow the steps below:

  1. Run the Jekyll server:

    $ ./bin/jekyll serve
  2. Open localhost:4000 in your browser.

Edit with Puma

For more programmatical pull requests (such as handling webhooks notifications via POST), Puma is necessary. To start and inspect your edits using Puma, follow the steps below:

  1. Run the Puma server:

    $ ./bin/puma
  2. Open localhost:9292 in your browser.

API Documentation

All Travis CI API V2 (and 2.1) documentation is maintained in slate/source and generated from the source at build time.

License

Distributed under the MIT license, like other Travis CI projects.