mirror of
https://github.com/LBRYFoundation/LBRY-Vault.git
synced 2025-08-27 23:41:35 +00:00
f5f3394552
If there is a collision between a branch name and a commit hash, git
will choose the branch, even if the full 40-hex-long commit hash is
given. GitHub disallows branches/tags with such a name but git itself
does not. By adding the `^{commit}` syntax sugar after a ref name,
we can tell git that we want the commit hash to be preferred,
and hence we don't need to trust GitHub (only git).
see https://security.stackexchange.com/questions/225411/
|
||
|---|---|---|
| .. | ||
| android | ||
| build-linux | ||
| build-wine | ||
| deterministic-build | ||
| osx | ||
| requirements | ||
| udev | ||
| build_tools_util.sh | ||
| freeze_packages.sh | ||
| make_download | ||
| make_libsecp256k1.sh | ||
| make_packages | ||
| pull_locale | ||
| push_locale | ||
| sign_packages | ||
| sign_version | ||
| upload | ||