diff options
| author | Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> | 2020-12-17 10:54:37 +0200 |
|---|---|---|
| committer | Hennadii Stepanov <32963518+hebasto@users.noreply.github.com> | 2020-12-18 01:15:53 +0200 |
| commit | 95487b055328b590ba83f258de9637ab0f9a2f17 (patch) | |
| tree | f8ff8e97cef3f8eb5ec242728bf6b6b2d97d1615 /doc | |
| parent | 09d105ef0f8b4b06bf248721a1209c9e16e9db75 (diff) | |
doc: Drop mentions of Travis CI as it is no longer used
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/developer-notes.md | 4 | ||||
| -rw-r--r-- | doc/release-process.md | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/doc/developer-notes.md b/doc/developer-notes.md index 9cb416bb30..1f29bfffc4 100644 --- a/doc/developer-notes.md +++ b/doc/developer-notes.md @@ -543,7 +543,7 @@ General Bitcoin Core - *Rationale*: RPC allows for better automatic testing. The test suite for the GUI is very limited. -- Make sure pull requests pass Travis CI before merging. +- Make sure pull requests pass CI before merging. - *Rationale*: Makes sure that they pass thorough testing, and that the tester will keep passing on the master branch. Otherwise, all new pull requests will start failing the tests, resulting in @@ -1036,7 +1036,7 @@ Scripted diffs -------------- For reformatting and refactoring commits where the changes can be easily automated using a bash script, we use -scripted-diff commits. The bash script is included in the commit message and our Travis CI job checks that +scripted-diff commits. The bash script is included in the commit message and our CI job checks that the result of the script is identical to the commit. This aids reviewers since they can verify that the script does exactly what it is supposed to do. It is also helpful for rebasing (since the same script can just be re-run on the new master commit). diff --git a/doc/release-process.md b/doc/release-process.md index cedb36d51d..92845bcc82 100644 --- a/doc/release-process.md +++ b/doc/release-process.md @@ -307,9 +307,9 @@ bitcoin.org (see below for bitcoin.org update instructions). - First, check to see if the Bitcoin.org maintainers have prepared a release: https://github.com/bitcoin-dot-org/bitcoin.org/labels/Core - - If they have, it will have previously failed their Travis CI + - If they have, it will have previously failed their CI checks because the final release files weren't uploaded. - Trigger a Travis CI rebuild---if it passes, merge. + Trigger a CI rebuild---if it passes, merge. - If they have not prepared a release, follow the Bitcoin.org release instructions: https://github.com/bitcoin-dot-org/bitcoin.org/blob/master/docs/adding-events-release-notes-and-alerts.md#release-notes |