Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reorg doc deploy step for new GITHUB_TOKEN permissions requirements #659

Merged
merged 2 commits into from
Feb 1, 2024

Conversation

bpkroth
Copy link
Contributor

@bpkroth bpkroth commented Feb 1, 2024

Fixes our documentation deploy step in the CI pipeline, which is currently failing due to a change to the default permissions of the GITHUB_TOKEN which is now read-only unless otherwise specified.

@bpkroth bpkroth requested a review from a team as a code owner February 1, 2024 20:48
@bpkroth bpkroth closed this Feb 1, 2024
@bpkroth bpkroth reopened this Feb 1, 2024
@bpkroth
Copy link
Contributor Author

bpkroth commented Feb 1, 2024

Original announcement:

‌GITHUB_TOKEN permissions changes
‌On February 1 the default permissions for the GITHUB_TOKEN from Read/Write to Read-only. This is a breaking change for workflows that haven't added a perms block to their workflows. It is on you and your team to prepare and take steps to avoid breaking your GitHub Actions build workflow.

@bpkroth bpkroth enabled auto-merge (squash) February 1, 2024 22:01
@bpkroth bpkroth merged commit 2dec03f into microsoft:main Feb 1, 2024
22 checks passed
@bpkroth bpkroth deleted the github-pages-deploy-fixup branch February 1, 2024 22:17
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