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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add explicit permissions to all workflows #5728

Draft
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

andrewlock
Copy link
Member

Summary of changes

  • Adds explicit permissions to all workflows

Reason for change

It's a best practice to explicitly specify required permissions for all workflows, and soon we'll have to

Implementation details

Worked through each workflow, trying to work out what it does and what permissions it needs

Test coverage

I wish

Other details

Please don't just 馃檲 approve this, it needs 馃憖 because it has the potential to break at critical times otherwise! The workflows that run as part of standard PRs should be fine, but anything that's rare/release specific needs properly understanding

@andrewlock andrewlock added the area:builds project files, build scripts, pipelines, versioning, releases, packages label Jun 24, 2024
@andrewlock andrewlock requested a review from a team as a code owner June 24, 2024 08:40
@lucaspimentel lucaspimentel requested a review from a team June 24, 2024 19:04
@andrewlock andrewlock force-pushed the andrew/ci/tweaks-to-github-actions branch from 9dacb11 to 86c37db Compare June 25, 2024 07:13
@andrewlock andrewlock marked this pull request as draft June 25, 2024 07:18
@andrewlock
Copy link
Member Author

Converted to draft, as we should check to see what the monitor comes up with before committing to this

andrewlock added a commit that referenced this pull request Jul 2, 2024
## Summary of changes

- Handle code freeze a bit more easily
- Allow overriding checks for integration version bump PRs

## Reason for change

- We have a lot of PRs these days
- Fixes a minor annoyance that the test package version bump PRs can't
be merged unless you rebase/force-merge, because the checks don't
automatically run

## Implementation details

Mostly copy-paste

## Test coverage

Meh

## Other details

Moved these from #5728 so
we can merge this one sooner
<!-- Fixes #{issue} -->

<!-- 鈿狅笍 Note: where possible, please obtain 2 approvals prior to
merging. Unless CODEOWNERS specifies otherwise, for external teams it is
typically best to have one review from a team member, and one review
from apm-dotnet. Trivial changes do not require 2 reviews. -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:builds project files, build scripts, pipelines, versioning, releases, packages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants