Allow edits from maintainers in PR #264

New Issue

GiteaMirror · 2025-11-02T03:16:29-06:00

GiteaMirror commented

2025-11-02 03:16:29 -06:00

Originally created by @rugk on GitHub (Jan 22, 2017).

It would be nice to introduce the same feature that GitHub now has:

As far as I understand it this allows maintainers of the main repo, where you submit a PR to, to push to your PR. So they can now improve your PR without having to wait that the creator of the PR fixes the issues.

upstream issue: https://github.com/gogits/gogs/issues/3762

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @rugk on GitHub (Jan 22, 2017). It would be nice to introduce the same feature that GitHub now has: ![prallowedits](https://cloud.githubusercontent.com/assets/11966684/19346855/def2cd6a-9145-11e6-9a5b-752adcc28494.png) As far as I understand it this allows maintainers of the main repo, where you submit a PR to, to push to your PR. So they can now improve your PR without having to wait that the creator of the PR fixes the issues. --- upstream issue: https://github.com/gogits/gogs/issues/3762 <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/41209468-allow-edits-from-maintainers-in-pr?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>

GiteaMirror added the type/feature issue/confirmed labels 2025-11-02 03:16:29 -06:00

GiteaMirror closed this issue

2025-11-02 03:16:29 -06:00

GiteaMirror commented

2025-11-02 03:16:30 -06:00

@bkcsoft commented on GitHub (Feb 12, 2017):

This might be a bit hard at the moment, since we now only map HasAccess(user, repo) and not HasAccess(user, repo, branch)... And we would have to check which branches are being pushed, which might lead to security issues 🙁

@bkcsoft commented on GitHub (Feb 12, 2017): This might be a bit hard at the moment, since we now only map `HasAccess(user, repo)` and not `HasAccess(user, repo, branch)`... And we would have to check which branches are being pushed, which might lead to security issues 🙁

GiteaMirror commented

2025-11-02 03:16:30 -06:00

@stale[bot] commented on GitHub (Feb 17, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Feb 17, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:16:30 -06:00

@wxiaoguang commented on GitHub (Apr 29, 2022):