Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge pull request #1 from TeamPorcupine/master #1515

Closed
wants to merge 1 commit into from
Closed

Merge pull request #1 from TeamPorcupine/master #1515

wants to merge 1 commit into from

Conversation

pele90
Copy link

@pele90 pele90 commented Oct 6, 2016

update from original

@pele90 pele90 closed this Oct 6, 2016
@mikejbrown
Copy link
Contributor

Okay if it's a wrong tutorial directing people to do this then something should be done about it. See #1507

And #1446 #1330 #1103 #717 #715 #591 #590 #491 #490 #475 #161 #160 #117

@bjubes
Copy link
Collaborator

bjubes commented Oct 7, 2016

What exactly causes these to occur?

@mikejbrown
Copy link
Contributor

According to @UnknownSoldier1 on #1507

Well, Quill has made in his first tutorial for contributing to GitHub that you can update your local repository by making a PR from this repository to your own local repository. When making a PR it is a little bit confusing if you pull the changes the correct way around which might result in exactly this happening. At least that was the reason for me, I assume thats the issue of other people as well.

There is no reason for people to make pull requests from TeamPorcupine to their own repository. If you want to pull, you just pull.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants