14
[help] So I cant' fork the fork of repo?
(sh.itjust.works)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 05 Aug 2023
14 points (85.0% liked)
Programming
16984 readers
241 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
You can add the even-cooler-stuff as another remote repo(like origin) and grab those changes and branch off of one of is branches then you can make pull requests to even cooler stuff from those branches.
https://stackoverflow.com/questions/7244321/how-do-i-update-or-sync-a-forked-repository-on-github
I'm pretty confident the reason GitHub isn't allowing you to fork the even-cooler-stuff repo is that technically they are the same repo... And multiple remotes should do the trick.
I blame GitHub for this. They invented this cool concept of a "fork" which is not technically a fork but only a stupid clone with another remote URL, and "pull request" which is basically a merge request with another name. It's confusing and seem to create problems across teams /rant
The name "pull request" is actually more accurate, because you ask the upstream repository to
git pullthe changes from the downstream repo.Either one works imo, as the maintainer is asked to merge your changes into his repo.
It's only more accurate because they actually put the fork in a "different" repo (which really is the same repo).
If you only have one repo like in Gitlab, merge request is more accurate.
https://docs.gitlab.com/ee/user/project/repository/forking_workflow.html
How is this different from GitHub?
Just to make sure there's no misunderstanding: When I want to contribute to a project I'm not involved in, like inkscape, I'm not allowed to create a branch in their repo, so I have to fork it, which creates a copy of the repo, and sets the original repo as a remote.
Note that git is a distributed VCS that doesn't distinguish between servers and clients. Forking and cloning are the same operation from a technical perspective, except when you
git clone, the copy ends up on your local machine, and when you press the "fork" button, the copy is on a GitHub/GitLab server.