diff options
| author |  Johannes Schindelin <johannes.schindelin@gmx.de> | 2020-10-07 08:17:49 +0000 |
|---|---|---|
| committer |  Junio C Hamano <gitster@pobox.com> | 2020-10-07 09:54:53 -0700 |
| commit | 17c13069b47e64fb3fdd4de57f87b80943be1e4d (patch) | |
| tree | 7b563dfb8dae82d8273e74fd25a9b6828165cc10 /Documentation/git-merge-tree.txt | |
| parent | Git 2.29-rc0 (diff) | |
| download | tgif-17c13069b47e64fb3fdd4de57f87b80943be1e4d.tar.xz | |
GitHub workflow: automatically follow minor updates of setup-msbuild
It is the custom to follow minor updates of GitHub Actions
automatically, by using the suffix `@v1`. Actions' maintainers will then
update that `v1` ref to point to the newest.
However, for `microsoft/setup-msbuild`, 889cacb6897 (ci: configure
GitHub Actions for CI/PR, 2020-04-11) uses a very specific `@v1.0.0`
suffix.
In this instance, that is a problem: should `setup-msbuild` release a
new version that intends to fix a critical bug, we won't know it, and we
won't use it.
Such a scenario is not theoretical. It is happening right now:
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands
Let's simplify our setup, allowing us to benefit from automatically
using the newest v1.x.
Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/git-merge-tree.txt')
0 files changed, 0 insertions, 0 deletions