-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Update permissions needed for github actions that run tests #20239
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
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
Review from Kyle-Neale is dismissed. Related teams and files:
- agent-integrations
- .github/workflows/test-fips-e2e.yml
- .github/workflows/test-target.yml
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-7.66.x 7.66.x
# Navigate to the new working tree
cd .worktrees/backport-7.66.x
# Create a new branch
git switch --create backport-20239-to-7.66.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 5657f0e31f408090072456264444e087b58d1ed3
# Push it to GitHub
git push --set-upstream origin backport-20239-to-7.66.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-7.66.x Then, create a pull request where the |
What does this PR do?
Github actions that run tests need to be able to read contents of branches that run tests. Additing the
id-token: write
permission stopped allowing any read permisisonsMotivation
Review checklist (to be filled by reviewers)
qa/skip-qa
label if the PR doesn't need to be tested during QA.backport/<branch-name>
label to the PR and it will automatically open a backport PR once this one is merged