Skip to content

Redirect workflow actions from upstream Azure/login to forked repository - #1

Draft
cloudesize67-cmd with Copilot wants to merge 2 commits into
masterfrom
copilot/create-azure-login-action-fork
Draft

Redirect workflow actions from upstream Azure/login to forked repository#1
cloudesize67-cmd with Copilot wants to merge 2 commits into
masterfrom
copilot/create-azure-login-action-fork

Conversation

Copilot AI commented Jan 31, 2026

Copy link
Copy Markdown

GitHub Actions workflows were referencing the upstream azure/login@v1 action instead of this fork. All workflows now use cloudesize67-cmd/login@master, making the fork self-contained.

Changes

  • azure-login-canary.yml: Updated 4 action references
  • azure-login-integration-tests.yml: Updated 8 action references

All instances of uses: azure/login@v1 replaced with uses: cloudesize67-cmd/login@master.

Note

Using @master branch reference since no version tags exist in the fork. Consider creating versioned releases (e.g., v1, v2) for reproducible builds in production workflows.

Original prompt

Make the fork from login to azure in github actions fork, a separate repository integrated into my repositorry.


✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

…d of azure/login@v1

Co-authored-by: cloudesize67-cmd <237356855+cloudesize67-cmd@users.noreply.github.com>
Copilot AI changed the title [WIP] Create Azure login action fork in separate repository Redirect workflow actions from upstream Azure/login to forked repository Jan 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants