The submodules are stored in .gitmodules: $ cat .gitmodules [submodule “ext/google-maps”] path = ext/google-maps url = git://git.naquadah.org/google-maps.git If you edit the url with a text editor, you need to run the following: $ git submodule sync This updates .git/config which contains a copy of this submodule list (you could also just edit the relevant [submodule] … Read more
After clicking “Insights” on top and then “Forks” on the left, the following bookmarklet prints the info directly onto the web page like this: The code to add as a bookmarklet (or to paste into the console): javascript:(async () => { /* while on the forks page, collect all the hrefs and pop off the … Read more
Just like GitHub, you have to pull the commits down to your own machine, merge, and then push them back to your fork on Bitbucket. If you go to your fork on Bitbucket you can click “compare fork” to get to a page where you see incoming and outgoing commits. If you go to the … Read more
The modern Git should able to detect remote branches and create a local one on checkout. However if you did a shallow clone (e.g. with –depth 1), try the following commands to correct it: git config remote.origin.fetch ‘+refs/heads/*:refs/remotes/origin/*’ git fetch –all and try to checkout out the branch again. Alternatively try to unshallow your clone, … Read more
For the record, recently I ran into this same problem and addressed it with Github Actions. The solution is rather easy: an scheduled action fetches the upstream repository and merges it into mine. # .github/workflows/example.yml name: Merge upstream branches on: schedule: # actually, ~5 minutes is the highest # effective frequency you will get – … Read more
There’s no GitHub way (small lie, see below), but there’s also nothing to fear. By definition, your fork of a fork is a fork of the original. When you open a pull request, you get the option to choose both the origin and the destination for your pull request. The choices available there obviously depend … Read more
Just create a new repository and push to it from your working copy: git clone git@github.com:me/myrepo-original cd myrepo-original git remote set-url origin git@github.com:me/myrepo-new git push origin master Now you have a new repository, myrepo-new, which is identical to myrepo-original.
I will answer this question using an example. I have a fork of TTTAttributedLabel with some extra functionality I added here: https://github.com/getaaron/TTTAttributedLabel In order to use this in a Cocoapods project, I: Push my changes to my fork Configure my Podfile to get the changes & update Once you’ve pushed your changes to your fork, … Read more
Think of it this way: The repo[sitory] corresponds to the collaborated work of the team across one or many branches. All contributors have their own copy of it. Each fork of the main repo corresponds to a contributor’s work. A fork is really a Github (not Git) construct to store a clone of the repo … Read more
If you just want to track changes, first make an empty repository in GitLab (or whatever else you may be using) and clone it to your computer. Then add the GitHub project as the “upstream” remote with: git remote add upstream https://github.com/user/repo Now you can fetch and pull from the upstream should there be any … Read more