-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Require approval to run actions for fork pull request #22803
Merged
lunny
merged 19 commits into
go-gitea:main
from
wolfogre:feature/actions_fork_pr_approval
Feb 24, 2023
Merged
Require approval to run actions for fork pull request #22803
lunny
merged 19 commits into
go-gitea:main
from
wolfogre:feature/actions_fork_pr_approval
Feb 24, 2023
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wolfogre
added
type/enhancement
An improvement of existing functionality
topic/gitea-actions
related to the actions of Gitea
labels
Feb 7, 2023
wolfogre
changed the title
Require approval for fork pull request
Require approval to run actions for fork pull request
Feb 7, 2023
delvh
added
topic/security
Something leaks user information or is otherwise vulnerable. Should be fixed!
and removed
topic/security
Something leaks user information or is otherwise vulnerable. Should be fixed!
labels
Feb 7, 2023
lunny
reviewed
Feb 16, 2023
GiteaBot
added
the
lgtm/need 2
This PR needs two approvals by maintainers to be considered for merging.
label
Feb 16, 2023
lunny
approved these changes
Feb 16, 2023
GiteaBot
added
lgtm/need 1
This PR needs approval from one additional maintainer to be merged.
and removed
lgtm/need 2
This PR needs two approvals by maintainers to be considered for merging.
labels
Feb 16, 2023
yardenshoham
added
the
outdated/backport/v1.19
This PR should be backported to Gitea 1.19
label
Feb 22, 2023
lunny
removed
the
outdated/backport/v1.19
This PR should be backported to Gitea 1.19
label
Feb 23, 2023
@yardenshoham This PR has one migration so that it cannot be backport to old version. |
On the other hand, what we could also do is merge #23078, and then backport it. |
That PR is not ready, we should be careful and need more discuss on that side. |
Zettat123
approved these changes
Feb 24, 2023
GiteaBot
added
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
and removed
lgtm/need 1
This PR needs approval from one additional maintainer to be merged.
labels
Feb 24, 2023
lunny
added
the
reviewed/wait-merge
This pull request is part of the merge queue. It will be merged soon.
label
Feb 24, 2023
lunny
removed
the
reviewed/wait-merge
This pull request is part of the merge queue. It will be merged soon.
label
Feb 24, 2023
zjjhot
added a commit
to zjjhot/gitea
that referenced
this pull request
Feb 24, 2023
* giteaoffical/main: Fix db.Find bug (go-gitea#23115) Avoid warning for system setting when start up (go-gitea#23054) Require approval to run actions for fork pull request (go-gitea#22803) Fix nil context in RenderMarkdownToHtml (go-gitea#23092) Add HesterG to maintainers (go-gitea#23104) improve FindProjects (go-gitea#23085)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
lgtm/done
This PR has enough approvals to get merged. There are no important open reservations anymore.
topic/gitea-actions
related to the actions of Gitea
type/enhancement
An improvement of existing functionality
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, Gitea will run actions automatically which are triggered by fork pull request. It's a security risk, people can create a PR and modify the workflow yamls to execute a malicious script.
So we should require approval for first-time contributors, which is the default strategy of a public repo on GitHub, see Approving workflow runs from public forks.
Current strategy:
2023-02-07.17.34.08.mov
GitHub has an option for that, you can see that at
/<owner>/<repo>/settings/actions
, and we can support that later.