mirror of
https://github.com/hashicorp/vault.git
synced 2026-02-03 20:40:45 -05:00
d1b34cf00c
When determining whether to skip a backport ref we currenly we have to
consider many factors:
- Whether or not there are changed files?
- If there are changed files, are some enterprise or CE?
- Are there some changed files that ought to be backported to inactive
branches?
- Is the target branch active or not?
We had a large test suite that covered _most_ of these cases but because
the changed file set determines a lot of behavior we were missing cases
where we ought to backport normal mixed changed file sets for no other
reason other than the branch is active. After fixing and normalizing the
tests I fixed the source bug which is that we didn't strip the branch
prefix from the ref version when checking branch activeness.
Signed-off-by: Ryan Cragun <me@ryan.ec>
Co-authored-by: Ryan Cragun <me@ryan.ec>
|
||
|---|---|---|
| .. | ||
| codechecker | ||
| pipeline | ||
| semgrep | ||
| stubmaker | ||
| tools.go | ||
| tools.sh | ||