Hi folks! I’m currently trying to learn a good workflow to fork a (say) github project and work on it on my forgejo. I have made forks and PRs in the past but I fail to see how to do it in this case, at least efficiently.
I could of course fork on github and mirror the repo on my forge. That would include me putting my work on github instead of only making a PR on github. I would prefer forking directly to my forge and sending only the PR on github. On the other hand, if I delete my fork afterward, it was pretty irrelevant to begin with.
How would you approach this?
Well, Pull Request is not a git feature, it’s a GitHub feature. So you can only make PRs from forks on GitHub. Whether you store your work on your own Forgejo as well is up to you but you can’t go around GitHub if you want to make PRs.
Request-pull, on the other hand is a native git feature. Just no one uses it AFAIK, and you’ll probably confuse anyone if you try.
You can push mirror your fork back to GitHub when you deem necessary (e.g when it’s in a good shape) and create a PR to the parent repo automatically using forgejo runner script, you’d just need to make an API token. If the goal is to automate PRs. If the goal is to not use GitHub for your forks but still continue to make PRs, you can’t work around that I think. Unless there’s a way to PR a bunch of patch files perhaps?
Fair enough! Thank you for the heads up. I will try and continue in that direction.
The runners are very exciting but I still need to understand how use them.
