Updating README with new verify-merge.py example.

This commit is contained in:
Jonathan Cross 2019-11-19 20:49:53 +01:00
parent 4f07f49849
commit a9da606f2a
No known key found for this signature in database
GPG key ID: D8578DF8EA7CCF1B

View file

@ -27,6 +27,6 @@ If you are committing for the first time, add your pgp public key to the `gitian
## Verifying Gitian Signatures
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`.
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`.
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.
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.