Skip to content

ci: avoid set-env#466

Merged
derrickstolee merged 2 commits intomicrosoft:mainfrom
dscho:dont-use-set-env-in-ci
Nov 17, 2020
Merged

ci: avoid set-env#466
derrickstolee merged 2 commits intomicrosoft:mainfrom
dscho:dont-use-set-env-in-ci

Conversation

@dscho
Copy link
Copy Markdown
Member

@dscho dscho commented Nov 17, 2020

This imitates git/git@cac42e471afa to avoid using the now-deprecated set-env construct in our CI workflow.

Just like we did in git/git in cac42e471afa (ci: avoid using the
deprecated `set-env` construct, 2020-11-07), we use the recommended
alternative described in the `set-env` deprecation announcement in
https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho dscho force-pushed the dont-use-set-env-in-ci branch from b0b85fa to bd225b3 Compare November 17, 2020 15:46
@dscho
Copy link
Copy Markdown
Member Author

dscho commented Nov 17, 2020

Yay PowerShell!

Just like `set-env`, we need to avoid using `add-path`.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
@dscho dscho force-pushed the dont-use-set-env-in-ci branch from 479d8af to c215cad Compare November 17, 2020 16:25
@derrickstolee derrickstolee merged commit d6518d5 into microsoft:main Nov 17, 2020
@dscho dscho deleted the dont-use-set-env-in-ci branch November 17, 2020 19:45
derrickstolee added a commit that referenced this pull request Dec 9, 2020
This updates on top of the 20.10.178 release.

Requires build updates from #466.

This actually updates to a better build:

1. It has a new tag `v2.29.0.vfs.0.1`.
2. It was created after `git-for-windows/build-extra` updated with the new GCM Core package.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants