releases/v2
main
users/vmjoseph/checkout-upgrade-1.1.3
fhammerl/bump-gh-package-versions
users/vmjoseph/no-proxy
vmjoseph/toolkit-windows-exec
dependabot/npm_and_yarn/qs-6.11.0
vmjoseph/silent-rev-parse
users/cory-miller/submodule-test
users/cory-miller/package-lock-sync
dependabot/npm_and_yarn/minimatch-3.1.2
ericsciple-patch-1
hross-zeit-vercel
master
users/ericsciple/m167ssh
users/ericsciple/m167workflow
users/ericsciple/m167sub
test-data/v2/submodule-ssh-url-level-2
test-data/v2/submodule-ssh-url
test-data/v2/submodule-ssh-url-level-1
test-data/v2/submodule
users/ericsciple/m166username
users/ericsciple/m166refs
users/tihuang/proxysupport
users/ericsciple/m164submodule
users/ericsciple/m163tarball_temp
users/ericsciple/m163tarball_efficient_download
users/ericsciple/m162pr
users/ericsciple/test-pr
test-data/v2/basic
test-data/v2/submodule-level-1
test-data/v2/submodule-level-2
test-data/v2/lfs
test-data/v2/side-by-side-2
test-data/v2/side-by-side-1
revert-56-users/tihuang/checkoutV1_1
releases/v1
Update-description
v2-beta
v1
v1.2.0
v1.1.0
1.0.0
v1.0.0
v2
v2.0.0
v2.1.0
v2.1.1
v2.2.0
v2.3.0
v2.3.1
v2.3.2
v2.3.3
v2.3.4
v2.3.5
v2.4.0
v2.4.1
v2.4.2
v2.5.0
v2.6.0
v2.7.0
v3
v3.0.0
v3.0.1
v3.0.2
v3.1.0
v3.2.0
v3.3.0
v3.4.0
v3.5.0
${ noResults }
1 Commits (c198d47ecd629cd5e345b58c947c90db217d856b)
Author | SHA1 | Message | Date |
---|---|---|---|
Cory Miller |
8856415920
|
Implement branch list using callbacks from exec function (#1045)
When trying to list local branches to figure out what needs cleaned up during runs on non-ephemeral Actions Runners, we use git rev-parse --symbolic-full-name to get a list of branches. This can lead to ambiguous ref name errors when there are branches and tags with similar names. Part of the reason we use rev-parse --symbolic-full-name vs git branch --list or git rev-parse --symbolic seems to related to a bug in Git 2.18. Until we can deprecate our usage of Git 2.18, I think we need to keep --symbolic-full-name. Since part of the problem is that these ambiguous ref name errors clog the Actions annotation limits, this is a mitigation to suppress those messages until we can get rid of the workaround. |
2 years ago |