Update configuring-openid-connect-in-azure.md
The version of the task doesn't exist so setting it to the newest version in the v2 family which works.
Why:
Closes:
What's being changed (if available, include any code snippets, screenshots, or gifs):
Check off the following:
- [ ] A subject matter expert (SME) has reviewed the technical accuracy of the content in this PR. In most cases, the author can be the SME. Open source contributions may require an SME review from GitHub staff.
- [ ] The changes in this PR meet the docs fundamentals that are required for all content.
- [ ] All CI checks are passing and the changes look good in the review environment.
How to review these changes 👓
Thank you for your contribution. To review these changes, choose one of the following options:
A Hubber will need to deploy your changes internally to review.
Table of review links
Note: Please update the URL for your staging server or codespace.
The table shows the files in the content directory that were changed in this pull request. This helps you review your changes on a staging server. Changes to the data directory are not included in this table.
| Source | Review | Production | What Changed |
|---|---|---|---|
actions/security-for-github-actions/security-hardening-your-deployments/configuring-openid-connect-in-azure.md |
fpt ghec ghes@ 3.17 3.16 3.15 3.14 3.13 |
fpt ghec ghes@ 3.17 3.16 3.15 3.14 3.13 |
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server
🤖 This comment is automatically generated.
Thanks for opening a PR! I'll get this triaged for review.
LGTM, could you resolve merge conflicts?
A stale label has been added to this pull request because it has been open 30 days with no activity. If you think this pull request should remain open, please add a new comment.
A stale label has been added to this pull request because it has been open 30 days with no activity. If you think this pull request should remain open, please add a new comment.
Yes this should stay opened
@wi5nia Would you be able to do a rebase or something else to resolve the conflicts? We changed the file structure of Actions and everything has gotten moved around. I might be able to figure out how to do it, but it would definitely be a git learning curve for me that would delay getting this merged further.
@wi5nia Would you be able to do a rebase or something else to resolve the conflicts? We changed the file structure of Actions and everything has gotten moved around. I might be able to figure out how to do it, but it would definitely be a git learning curve for me that would delay getting this merged further.
what? why? I just did a fork of GH official documentation and corrected the wrong information. I have no clue about the file structure or anything...
@Sharra-writes - I created a new PR if that makes any difference for you - https://github.com/github/docs/pull/40200
@wi5nia That should work. It's nothing you did, we just changed a bunch of things that made this complicated. I know it's possible to fix, I'm even pretty sure it's something I could fix for you, it's just not something I've learned yet. I'll close this PR and get your new one approved.