934dd88d3b
This makes now the same simplification as the chromium release scripts do. For creating branch B from a gnumbd'ed (aka real) commit X do: 1. Branch Y off the real X 2. Set refs/pending/heads/B to Y 3. Set refs/pending-tags/B to X 4. Set refs/heads/B to X The old algorithm tried to branch off the pending correspondent of X. That commit was determined by comparing tree objects of the real X and commits on pending. Unfortunately, multiple commits on one branch can refer to the same tree object, e.g., for commits P, Q, R with R being the revert of Q, P and R refer to the same tree object. TBR=tandrii@chromium.org NOTRY=true TEST=./script_test.py TEST=tools/release/create_release.py -a me -r you --dry-run Review URL: https://codereview.chromium.org/979243004 Cr-Commit-Position: refs/heads/master@{#27042} |
||
---|---|---|
.. | ||
auto_push.py | ||
auto_roll.py | ||
auto_tag.py | ||
check_clusterfuzz.py | ||
chromium_roll.py | ||
common_includes.py | ||
create_release.py | ||
git_recipes.py | ||
merge_to_branch.py | ||
push_to_candidates.py | ||
releases.py | ||
script_test.py | ||
test_scripts.py |