You can create a new, fresh history quite easily in Git. Let’s say you want your master branch to be the one that you will push to GitHub, and your full history to be stored in old-master. You can just move your master branch to old-master, and then start a fresh new branch with no … Read more
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
Another option is to use Gitlab’s export/import feature. Existing projects running on any GitLab instance or GitLab.com can be exported with all their related data and be moved into a new GitLab instance. The difference with the other answer is that it also copies the following: Exported contents The following items will be exported: Project … Read more
I don’t think you can fork your own repo. Clone it and push it to a new repo is good but you need to: git clone https://github.com/userName/Repo New_Repo cd New_Repo git remote set-url origin https://github.com/userName/New_Repo git remote add upstream https://github.com/userName/Repo git push origin master git push –all (see git push) See the all process described … Read more
You can limit the depth of the history while cloning: –depth <depth> Create a shallow clone with a history truncated to the specified number of revisions. Use this if you want limited history, but still some.
You’re doing the right thing. cd ~/Sites/ git clone ~/Dev/markupDNA/ project-N cd project-N git remote rename origin markupDNA Nav to the folder where you store your projects clone your base markupDNA repo with custom name rename the remote so that if you want to an ‘origin’ later, you can
Try npm install <ghusername>/<repoName>, where <ghUsername> is your GitHub username (without the @) and <repoName> is the name of the repository. That should correctly install it. You will most likely want to use the –save or –save-dev flag with the install command to save dependency in your package.json. If that isn’t working correctly, check the … Read more
Fork, in the GitHub context, doesn’t extend Git. It only allows clone on the server side. When you clone a GitHub repository on your local workstation, you cannot contribute back to the upstream repository unless you are explicitly declared as “contributor”. That’s because your clone is a separate instance of that project. If you want … Read more
(In addition to the official “GitHub Help ‘Using pull requests’ page“, see also “Forking vs. Branching in GitHub“, “What is the difference between origin and upstream in GitHub“) Couple tips on pull-requests: Assuming that you have first forked a repo, here is what you should do in that fork that you own: create a branch: … Read more
How do I update or sync a forked repository on GitHub?