e1a5744 devtools: Auto-set branch to merge to in github-merge (Wladimir J. van der Laan)
7d0542c devtools: make github-merge.py use py3 (Wladimir J. van der Laan)
31f53d8 [copyright] add MIT license headers to .sh scripts where missing (isle2983)
2862e18 Add README for verify-commits (Peter Todd)
c2d1d62 Remove pointless warning (Peter Todd)
befe6a5 Make verify-commits path-independent (Matt Corallo)
acb55dd Make verify-commits POSIX-compliant (Matt Corallo)
fe83a6d Allow to whitelist commits signed with a revoked key (Matt Corallo)
e1873f6 Adjust verify-commits to gitian-builder (MarcoFalke)
3be7a42 Fix pre-push-hook regexes (Matt Corallo)
73f6969 Add script to verify all merge commits are signed (Matt Corallo)
As we are already using the API to retrieve the pull request
title, also retrieve the base branch.
This makes sure that pull requests for 0.12 automatically end up in
0.12, and pull requests for master automatically end up in master,
and so on.
It is still possible to override the branch from the command line
or using the `githubmerge.branch` git option.
This makes github-merge.py the first developer tool to go
all Python 3 (for context see #7717).
The changes are straightforward as the script already was
`from __future__ import division,print_function,unicode_literals`.
However urllib2 changed name, and json will only accept unicode data not
bytes.
This retains py2 compatibility for now: not strictly necessary
as it's not used by the build system - but it was easy.
Any attacker who managed to make an evil commit that changed something in the
contrib/verify-commits/ directory could just as easily remove the warning
and/or modify it to not display the evil commits; telling the user to check
those commits specifically misleads them into checking just those commits
rather than the script itself.
It can be confusing to new users for make-base-vm to create a lucid vm
by default, so switch to xenial, which is also a LTS release, but isn't
EOL yet. Using lucid with gitian-builder is broken anyway, because
lucid has been moved to old-releases.ubuntu.com since it is EOL and
gitian-builder doesn't support old-releases.ubuntu.com.
So you can make local copy of /usr/share/debootstrap/ and
e.g. add there missing e.g. "xenial" or other script/template,
without mucking around in system directory managed by
package manager.
This file is outdated, the mentioned issue is no longer there for
newer gcc versions - for bitcoin we haven't had to specify any special
optimization flag overrides for a long time (we compile using -O2).
- apropos to a discussion about merge request #36, added a flag in the descriptor and command line flag.
- adding sudo: true in the yml file plus adding a command line flag --allow-sudo will allow script user to elevate permissions with no password.
784d878 Adjust readme for gitian-builder (MarcoFalke)
ee6dee4 devtools: Fix utf-8 support in messages for github-merge (Wladimir J. van der Laan)
7d99dee [devtools] github-merge get toplevel dir without extra whitespace (Andrew C)
0ae5a18 devtools: show pull and commit information in github-merge (Wladimir J. van der Laan)
992efcf devtools: replace github-merge with python version (Wladimir J. van der Laan)
Use 'utf-8' instead of the Python 2 default of 'ascii' to encode/decode
commit messages.
This can be removed when switching to Python 3, as 'utf-8' is the
default there.
Necessary for merging #7422 due to the ฿ in ฿tcDrak.
This is meant to be a direct translation of the bash script,
with the difference that it retrieves the PR title from github,
thus creating pull messages like:
Merge #12345: Expose transaction temperature over RPC
Now, if a user is using something like on-target directly, that user
doesn't need to set the DISTRO or TUSER variables if using Ubuntu guests
(so the scripts function the same as they did before Debian guest
support was added).
Devrandom
Kevin Gallagher
Wladimir J. van der Laan
isle2983
Peter Todd
Matt Corallo
MarcoFalke
Nicolas Vigier
Joseph Bisch
Tigusoft Admin
Chris Kleeschulte
Andrew C
Dev Random
Luke Dashjr