Commit a9da606f2a27afef5c55c75cffebba9bef323dd8
Updating README with new verify-merge.py example.
Jonathan Cross committed on 11/19/2019, 7:52:53 PMParent: 4f07f49849f38cd4722626a72ca316fd9c39f28d
Files changed
| README.md | changed |
| README.md | ||
|---|---|---|
| @@ -26,7 +26,7 @@ | ||
| 26 | 26 | If you are committing for the first time, add your pgp public key to the `gitian-pubkeys` directory in armored ASCII format and a filename of `username.asc`. |
| 27 | 27 | |
| 28 | 28 | ## Verifying Gitian Signatures |
| 29 | 29 | |
| 30 | -The `verify-merge.py` script can be used to verify existing gitian sigs. For example to verify all the signatures on the v0.14.1.0 assert files, run `./verify-merge.py v0.14.1.0`. More information on how to use the script can be found by running `./verify-merge.py --help`. | |
| 30 | +The `verify-merge.py` script can be used to verify existing gitian signatures and assert file contents (hashes of binaries). By default, it will check all releases. You can also specify a particular version to check, eg: `./verify-merge.py --version v0.14.1.0`. More information on how to use the script can be found by running `./verify-merge.py --help`. | |
| 31 | 31 | |
| 32 | -It is also possible to use the script to check the signatures of open pull requests. For example for pull request id 12 on github: `./verify-merge.py --pull_id 12 v0.14.1.0`. Be aware that running this will change the content of your git tree by creating a new `$pull_id_head` and `$pull_id_base` branch. The script deletes these branches again on exit. | |
| 32 | +It is also possible to use the script to check the signatures of open pull requests. For example for pull request id #12 on github: `./verify-merge.py --pull_id 12`. Be aware that running this will change the content of your git tree by creating a new `$pull_id_head` and `$pull_id_base` branch. The script deletes these branches again on exit. | |
Built with git-ssb-web