Skip to content

Adapt to recent codeowners changes - #9

Merged
mzruya merged 3 commits into
mainfrom
mz.adapt_recent_changes
Apr 11, 2023
Merged

Adapt to recent codeowners changes#9
mzruya merged 3 commits into
mainfrom
mz.adapt_recent_changes

Conversation

@mzruya

@mzruya mzruya commented Apr 11, 2023

Copy link
Copy Markdown
Contributor

Catches up on the recent behavior changes to the ruby implementation:

  • Omit unowned files early in the process and avoid the validation/file generation steps having to know about it.
  • Instead of omitting ignored teams, comment out their code owners entries
  • Change vendored gems entry to be a /**/** glob.

@mzruya
mzruya force-pushed the mz.adapt_recent_changes branch from 687c57b to dd04ae0 Compare April 11, 2023 15:06

@alexevanczuk alexevanczuk left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Cool to be reviewing rust code :)

@mzruya
mzruya merged commit ce8baa8 into main Apr 11, 2023
@mzruya
mzruya deleted the mz.adapt_recent_changes branch April 11, 2023 15:30
dduugg added a commit that referenced this pull request Aug 17, 2026
Resolves the eight open `actions/missing-workflow-permissions` CodeQL
alerts (#1, #3, #4, #5, #6, #7, #8, #9). Every job now has an effective
`permissions:` block scoped to what it actually does.

ci.yml
  Workflow-level `contents: read` covers `check`, `test` and `lints`,
  which only check out the repo and run cargo check/test/fmt/clippy.

  Four jobs override to `contents: write` because they mutate releases:
  - `release` runs `gh release create --generate-notes`
  - `upload-mac-universal-bin` and `upload-linux-bin` run
    `gh release upload` to attach the built tarballs
  - `generate-dotslash-files` uses facebook/dotslash-publish-release,
    which also publishes via `gh release upload`

audit.yml
  `rustsec/audit-check` needs `checks: write` to publish the advisory
  status check on push/pull_request runs and `issues: write` to open an
  issue per new advisory on the weekly scheduled run (both documented in
  the action's README). `contents: read` covers actions/checkout. It
  does not upload SARIF, so no `security-events: write`.

codeql.yml already declares permissions and is untouched.
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