Understanding and using the "Fork & Pull" model is essential for distributed software development, IMHO.
-
Jan Wildeboer 😷:krulorange:replied to Fluchtkapsel last edited by [email protected]This post is deleted!
-
Braw ☕🏳️🌈replied to Jan Wildeboer 😷:krulorange: last edited by
@jwildeboer I hate that we made forking necessary to work collaboratively on Git
-
Jan Wildeboer 😷:krulorange:replied to Fluchtkapsel last edited by [email protected]This post is deleted!
-
Jan Wildeboer 😷:krulorange:replied to Braw ☕🏳️🌈 last edited by [email protected]This post is deleted!
-
Jan Wildeboer 😷:krulorange:replied to Jan Wildeboer 😷:krulorange: last edited by [email protected]
I think that working collaboratively with Pull Requests as abstraction layer is totally worth it. And soon(tm) we will be able to collaborate that way using #ActivityPub to connect between different, decentralised forges, getting rid of the need to have accounts everywhere
#Forgejo (and other forges) are working on implementing #ForgeFed https://forgefed.org for that 5/6 -
Jan Wildeboer 😷:krulorange:replied to Jan Wildeboer 😷:krulorange: last edited by
Which brings me back to why I started this thread: The #ForkAndPull approach as part of the #C4process in times of decentralised forges. But that's a different and longer story that I hope to develop at https://c4process.wildeboer.net
6/6 -
Aleksandra Fedorova :fedora:replied to Jan Wildeboer 😷:krulorange: last edited by
@jwildeboer I still think that "Clone and Pull" model would be superior for drive-by contributors. "Fork" usually means overhead of long-term maintenance of your own "version" of a project in your own space, while often you just want to send a change request one time, not to become a real admin of your own full copy.
But that's an implementation detail.
-
Jan Wildeboer 😷:krulorange:replied to Jan Wildeboer 😷:krulorange: last edited by
(I admit I was a bit disappointed when I looked for a short and practical explanation of #ForkAndPull. Most articles I found dived deep into branches, rebases and merge conflicts. Which are important, but also overwhelming, if you just start to work with git and a forge. I hope this thread helps you to find out that you can do this too and with a bit of exercise it becomes a natural reflex
-
Jan Wildeboer 😷:krulorange:replied to Aleksandra Fedorova :fedora: last edited by [email protected]This post is deleted!
-
@brawaru Forgejo also supports a method without forking - AGit
https://forgejo.org/docs/latest/user/agit-support/
@jwildeboer -
Jan Wildeboer 😷:krulorange:replied to Beowulf last edited byThis post is deleted!
