#143 make live editor automatically fork repository and submit pull request

Open
opened 3 months ago by vimuser · 3 comments

when someone without push access to a repo clicks the Edit button on a file, they are told to fork the repository and use the live editor in their fork

what i think it should do instead (for a repo that someon doesn't have push access to):

  • auto-fork the repo
  • automatically create a branch (in their fork, automatically created) with their changes once they submit it
  • automatically generate pull request on the repo that they forked (so, the main repo, not their fork)

i was told to request this upstream, but upstream gogs uses github and i don't want to create an account there

with such a feature, people who don't want to use git directly can, for instance, easily submit fixes to documentation on a repository.

use-case: libreboot.org - it has edit buttons on every page, but currently it links to instructions for manually forking the repo (where the documentation for libreboot is) and submitting a pull request manually.

What I'd like to do is make those edit buttons link directly (for each page) to the corresponding file in the libreboot git repository via notabug's live editor, to make the libreboot website more like a real wiki, without the user having to manually fork the repo into their own notabug account (the automation would do that for them, and their changes that they make would automatically appear in the official libreboot repo as a pull request)

such a feature in gogs will help many projects, not just libreboot

when someone without push access to a repo clicks the Edit button on a file, they are told to fork the repository and use the live editor in their fork what i think it should do instead (for a repo that someon doesn't have push access to): * auto-fork the repo * automatically create a branch (in their fork, automatically created) with their changes once they submit it * automatically generate pull request on the repo that they forked (so, the main repo, not their fork) i was told to request this upstream, but upstream gogs uses github and i don't want to create an account there with such a feature, people who don't want to use git directly can, for instance, easily submit fixes to documentation on a repository. use-case: libreboot.org - it has edit buttons on every page, but currently it links to instructions for manually forking the repo (where the documentation for libreboot is) and submitting a pull request manually. What I'd like to do is make those edit buttons link directly (for each page) to the corresponding file in the libreboot git repository via notabug's live editor, to make the libreboot website more like a real wiki, without the user having to manually fork the repo into their own notabug account (the automation would do that for them, and their changes that they make would automatically appear in the official libreboot repo as a pull request) such a feature in gogs will help many projects, not just libreboot
Leah Rowe commented 3 months ago
Poster

this could either change the behaviour of the current edit button, or it could mean adding an extra, special edit button that behaves as described

this could either change the behaviour of the current edit button, or it could mean adding an extra, special edit button that behaves as described
zPlus commented 3 months ago

Reference to upstream issue: https://github.com/gogits/gogs/issues/4560

Reference to upstream issue: https://github.com/gogits/gogs/issues/4560
zPlus commented 3 months ago

I don't like the idea "automatically fork" the repository, it just wastes resource if they click by mistake, and takes long time if repository is big.

Otherwise, looks good to me.

Reply from upstream.

> I don't like the idea "automatically fork" the repository, it just wastes resource if they click by mistake, and takes long time if repository is big. > > Otherwise, looks good to me. Reply from upstream.
Sign in to join this conversation.
No Milestone
No assignee
2 Participants
Loading...
Cancel
Save
There is no content yet.