EIPs
EIPs copied to clipboard
GitHub actions don't run for first time contributors
Pull Request
https://github.com/ethereum/EIPs/pull/5164
What happened?
eipw and friends didn't run automatically for this PR since this is the authors first time contributing.
Relevant log output
No response
This is due to ~~a branch protection rule~~ a setting. CC @MicahZoltu @lightclient

I don't think so. I think this is just the default for GitHub actions.
Any idea what happens if a first-time-contributor submits a PR that touches a .workflow file, such as to print out secrets? While the number of second time editors to this repo is incredibly high, at least the current setup makes it a little harder to execute such an attack...
We should probably limit the set of actions that can be run to protect against that attack vector more broadly, though I think there are actions that let you run arbitrary shell commands so I'm not sure that would help much.
Needs reopening.
We should probably limit the set of actions that can be run to protect against that attack vector more broadly, though I think there are actions that let you run arbitrary shell commands so I'm not sure that would help much.
The prescience of this comment is alarming. 😬
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
Still an issue.
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
Still an issue.
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
Still an issue :|
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
Still an issue
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
Still an issue.
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
Still an issue.
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
Still an issue.
What do we need to do to resolve this?
Unsure.
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
Still an issue :|
There has been no activity on this issue for 1 week. It will be closed after 3 months of inactivity.
I think this is still an issue.
I actually haven't seen this happen recently, so I'll assume that something solved this.