-
Notifications
You must be signed in to change notification settings - Fork 725
ci(e2e): use GITHUB_TOKEN for GHCR e2e #1554
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| rules: | ||
| # rule does not apply to reusable worfklows where permissions are defined by | ||
|
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. ah, right; so wouldn't it still make sense to set defaults, or won't that work?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yeah that won't work unfortunately, see docker/github-builder#24
Member
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. That's annoying! Is it a known issue in zizmor? Is this something that could be fixed in GitHub actions itself?
Member
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think this is tracked inb zizmor yeah |
||
| # the caller workflow and not the reusable workflow itself | ||
| excessive-permissions: | ||
| ignore: | ||
| - .e2e-run.yml | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why was this removed?
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because we introduce
packages: writeand caller should take care of permissions, not the reusable workflow. There is some analysis here: docker/github-builder#24