I _guess_ that Github compares all the history of your branch with all
the history of upstream and find any merge commit.
The easiest and quickest way is starting from scratch, so you are sure
that the master branch in your fork is clean.
Il giorno mer 14 mag 2014 alle 21:37, Knute Snortum
<ksnor...@gmail.com> ha scritto:
I have done a git reset --hard on my local repository. Then I setup
one branch and one file to commit. I pushed this out to my GitHub
repository. When I try to do a pull request, I get nine commits
(from when I was merging back to the master branch) and four files.
I only need two commits and one file.
I haven't done GitHub pull requests before so I may be doing
something wrong. It seems to me that my GitHub repository still sees
the commits to master as changes that need to be in the pull request.
How can I clean out my GitHub repository? Or, how do I get a pull
request that has only the changes I want in it?
On Wed, May 14, 2014 at 11:34 AM, Knute Snortum <ksnor...@gmail.com>
I have pulled out all the ly files I have been working on and stowed
them. I'll put them back one by one when my repository is clean.
Then hopefully I will be able to create clean pull requests.
BTW, I found out how to delete a pull request: close it first. I
had assumed "Close" meant the comments.
On Wed, May 14, 2014 at 11:30 AM, Glen Larsen <glenl....@gmail.com>
On Wed, May 14, 2014 at 11:23 AM, Knute Snortum
Thanks Felix, I'll try that.
If I can close a pull request, I don't see how to on GitHub. I
may just be missing it, though. If anyone knows how to do it,
please tell me.
Closing is a product of merging the pull request. I believe if you
delete the branch of the pull request in your remote fork it will
effectively cancel/remove the pull request.
I am assuming you still have the topic branch in your local
Mutopia-discuss mailing list