Re: [git-users] Changes to be done in local repository if pull request is closed

2015-11-02 Thread Gergely Polonkai
Hello, in this case, you should have done a rebase instead of a merge, i.e. git pull --rebase insted of merely git pull. This way your commits would get replayed on top of the others, and no merge commit would exist. Best, Gergely On 3 Nov 2015 07:34, "Pranit Bauva"

[git-users] Changes to be done in local repository if pull request is closed

2015-11-02 Thread Pranit Bauva
Hey all! I am familiar with git but new to collaboration on project on github. I forked a repo (learnxinyminutes-docs) to make changes. I cloned it locally and made the required changes in the master branch only and committed it. Then I sent a pull request which got rejected. Now the project

Re: [git-users] Remove .git folder from Master Repo

2015-11-02 Thread Nelson Efrain A. Cruz
Hi. Whenever you clone (git clone) a git repo you get a repository, this means that you can't use git init because it's already a repo and you will have the .git folder. Now what you may want it's to discard the repo history, it's that what you want? El lun., 2 de nov. de 2015 a la(s) 8:02 a. m.,

Re: [git-users] Remove .git folder from Master Repo

2015-11-02 Thread Gergely Polonkai
git clone effectively does the following: mkdir projectdir cd projectdir git init git remote add origin projecturl git fetch origin git checkout -b master origin/master (of course, it's a bit more complicated, but it comes down to this) As you see, there is a "git init" there, which, among