-
Notifications
You must be signed in to change notification settings - Fork 169
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
Restrict Forked PRs by Default in Open-Source Screwdriver #3245
Comments
@kumada626 - we are aware that PRs coming from your group normally are created through fork. And we would like to add all of your team members to be the admins of the open source instance. So this should allow all of your members to be able to run PR jobs manually. What do you think? Here is the list of your team members that we are aware, please confirm the active members and let us know if we need to add any others. |
@VonnyJap I have no concerns about adding our team members to admin as long as there are no problems on your side. |
@kumada626 - I have added yourself and below members as admins @yk634 And I have also turned the default restrict PR run on the Screwdriver instances. |
@VonnyJap Thank you for adding members to the admins of the open source instance. |
@VonnyJap |
@foxtrot0304 - can you now attempt to access cd.screwdriver.cd with your Github account? I have just provisioned the access.
Yes, they are separate permissions. |
@kumada626 - I will add members who belong to the LY team as admins as well. Can you please confirm that all of them are still the active members and maintainers of Screwdriver? Thanks. |
@VonnyJap |
What happened:
We recently learned that there was an attempt from Security researcher to exploit secrets that are stored in Screwdriver pipeline by issuing a PR as described here.
What you expected to happen:
We are proactively updating the default settings in the open-source Screwdriver to restrict forked PRs from running on trigger, preventing such attempts in the future.
How to reproduce it:
Please refer to the PR link above.
The text was updated successfully, but these errors were encountered: