Skip to content

Commit 63129f6

Browse files
committed
Clean up documentation
1 parent 692c7a0 commit 63129f6

File tree

2 files changed

+4
-15
lines changed

2 files changed

+4
-15
lines changed

Rakefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ namespace :book do
77
end
88

99
# Variables referenced for build
10-
version_string = ENV['TRAVIS_TAG'] || `git describe --tags`.chomp
10+
version_string = `git describe --tags`.chomp
1111
if version_string.empty?
1212
version_string = '0'
1313
end

TRANSLATING.md

Lines changed: 3 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -72,22 +72,11 @@ On https://git-scm.com, the translations are divided into three categories. Once
7272
| Partial translations available in | up to chapter 6 has been translated. |
7373
| Full translation available in |the book is (almost) fully translated. |
7474

75-
## Continuous integration with Travis CI
75+
## Continuous integration with GitHub Actions
7676

77-
Travis CI is a [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) service that integrates with GitHub. Travis CI is used to ensure that a pull-request doesn't break the build or compilation. Travis CI can also provide compiled versions of the book.
77+
GitHub Actions is a [continuous integration](https://en.wikipedia.org/wiki/Continuous_integration) service that integrates with GitHub. GitHub Actions is used to ensure that a pull-request doesn't break the build or compilation. GitHub Actions can also provide compiled versions of the book.
7878

79-
Setting up Travis CI requires administrative control over the repository.
80-
81-
### Registering for Travis continuous integration
82-
83-
1. Register a Travis account [here](https://travis-ci.org/).
84-
1. Register your project in Travis.
85-
Please refer to the [Travis documentation](https://docs.travis-ci.com/) for more information.
86-
87-
### Setting up your repository for continuous integration
88-
89-
Travis CI works by scanning your project's root directory for a file named `.travis.yml` and following the 'recipe' that it contains. The good news is: there's already a working `.travis.yml` file in the Pro Git 2 source [here](https://raw.githubusercontent.com/progit/progit2-pub/master/travis.yml).
90-
Copy that file, and put it in your working directory. Commit the .yml file and push it to your translation repository; that should fire up a compilation and a check of the book's contents.
79+
If you keep the `.github` directory from the root repository, you should get the GitHub Action CI setup for free.
9180

9281
## Setting up a publication chain for e-books
9382

0 commit comments

Comments
 (0)