@Dirk + @Lars

As noted before, its all git (gerrit/gihub/...) and gerrit also don't work without special git configs for fetch/push


To replicate similar behavior you should be able to do something like this (untested as I simply sync forks from time to time with an automatic script like described here [1]):


1) fork the repro + checkout the "master" (not your fork!)
2) add your fork as a new origin (you can call it 'gerrit' just for convenience ;-)
3) create a new branch from master and apply your changes
4) push the branch to 'gerrit' origin
5) Click the link "create PR'
6) repeat 4-5 as necessary (NO NEED TO FORCE PUSH!)
7) when your changes are merged, simply pull (even after months) the master and repeat from 3, if you like click the "delete branch link"


[1] https://docs.github.com/en/github/collaborating-with-issues-and-pull-requests/syncing-a-fork


Am 18.03.21 um 14:12 schrieb Lars Vogel:
Hi Dirk,

  For GitHub projects I always need to fork, update my fork, create the PR, 
force push on every review comment.

I also find the Github process ackwards for contributions to other
repos, not sure why Github does not allow a simple way of
synchronization of forks.
But as a committer you have a simpler process. You could also create
PR from the repo directly, e.g. push to a new branch in the repo and
create a PR within the same directory. This reduces the work for
committers but still leaves the problem that contributors have to go
through the steps you described. Maybe there is a simpler way, as this
process seems quite popular but I don't know it.

On Thu, Mar 18, 2021 at 1:03 PM Dirk Fauth via platform-dev
<[email protected]> wrote:



Mickael Istria <[email protected]> schrieb am Do., 18. März 2021, 12:00:


I have the impression that the majority of committers who also happen to use 
GitHub for other (Eclipse or not) projects do agree that GitHub is an 
enhancement for the project community at large over Gerrit.


I disagree! Once Gerrit is setup for the project in my ide I simply contribute. 
And I can even simply contribute months later after a simple pull. For GitHub 
projects I always need to fork, update my fork, create the PR, force push on 
every review comment. For me it is much more work to contribute on a GitHub 
project everytime. Gerrit maybe takes more time at the beginning, but much less 
on the way.

Just my two cents.

Greez,
Dirk

_______________________________________________
platform-dev mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev



_______________________________________________
platform-dev mailing list
[email protected]
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Reply via email to