-
Notifications
You must be signed in to change notification settings - Fork 158
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
chore(ci): extend external contribution to all pr workflows #1985
Conversation
This approach allows checkout public and private repository, like Slab, without to worry too much about secret leakage under certain circumstances (e.g. under pull request from forks). The token has just read access on selected repositories.
a1ef455
to
18d82d6
Compare
18d82d6
to
c863941
Compare
@soonum lint and checks not happy ? |
Ok, I see what's going on here. I need to remove the dynamic referencing of workflow calls. |
there is a whitelist for the dep pinning |
c863941
to
21fde64
Compare
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.
it looks good to me, thanks!
21fde64
to
f41b9b6
Compare
f41b9b6
to
917bfb9
Compare
917bfb9
to
2958b15
Compare
User permission checking is done after the should-run, when there is such step, rather than before it. This way, only workflows that should run would fail id triggering actor is not allowed to launch it. Thus a repository maintainer would have to re-run only a handful of jobs that would effectively run afterward (i.e relevant code has changed and setup-instance would be called).
2958b15
to
2f80782
Compare
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.
Looks good to me, good job!
User permission checking is done after the should-run, when there is such step, rather than before it.
This way, only workflows that should run would fail id triggering actor is not allowed to launch it.
Thus a repository maintainer would have to re-run only a handful of jobs that would effectively run afterward.
Resolves: zama-ai/tfhe-rs-internal#890