You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Changed
One SSH submodule fetch for the build and the tests job. The 50-line
"Fetch submodules over SSH" step was copied verbatim into reusable-build-platform.yml and reusable-unity-tests.yml. It is now scripts/common/fetch_submodules_ssh.sh. To run it, both jobs check the
toolkit out right after the project checkout: earlier than before in the
build job, and in the tests job also when submodule-auth is ssh, not
only on the native lanes.
The Windows Git Bash step stays a copy, held identical by a test. It
runs before any checkout, because it sets core.longpaths for the project
checkout, which would clean away a toolkit checked out first. So it cannot
come from the toolkit. tests/test_shared_job_steps.py fails when the two
jobs' copies differ.
One way to get the bot token. Seven workflows carried the same ~55
lines of Node.js that signed a GitHub App JWT and exchanged it for an
installation token: auto-merge, auto-release, version-bump, build-pr-comment, license-rotation, sync-org-variables and unity-generate-license. They now use actions/create-github-app-token,
pinned to v3.2.0 by SHA, with the same scope (the whole installation on
the repository owner). It needs no checkout (most of them mint the token
before checking out), masks the token, and revokes it when the job ends. unity-generate-license still skips with a "set it by hand" warning when APP_ID / APP_PRIVATE_KEY are absent. The action prefers client-id
over the deprecated app-id; switching needs an APP_CLIENT_ID secret.