Skip to content
This repository has been archived by the owner on Aug 20, 2023. It is now read-only.

Add instructions on keeping fork up to date with upstream repo #340

Closed
gerhynes opened this issue Oct 4, 2019 · 3 comments
Closed

Add instructions on keeping fork up to date with upstream repo #340

gerhynes opened this issue Oct 4, 2019 · 3 comments

Comments

@gerhynes
Copy link
Contributor

gerhynes commented Oct 4, 2019

The contributing docs are really excellent and beginner-friendly.

One issue that contributors might run into during Hacktoberfest is that new commits by other contributors could make their fork go out of sync with the upstream repository before they have finished their own pull request.

Adding a link to GitHub's instructions on syncing a fork, or a paragraph with similar instructions, could be useful.
@welcome
Copy link

welcome bot commented Oct 4, 2019

Thank you so much for opening your first issue for this project! We'll try to get back to it as quickly as possible. While you are waiting...here's a random picture of a corgi (powered by dog.ceo)

picture of dog

@apennell apennell mentioned this issue Oct 5, 2019
Closed
@thatrobotdev thatrobotdev mentioned this issue Oct 5, 2019
Merged
2 tasks
@thatrobotdev
Copy link
Contributor

thatrobotdev commented Oct 5, 2019 •
edited

I'll take this one! :D #436

dkundel pushed a commit that referenced this issue Oct 5, 2019
@thatrobotdev @dkundel
docs(contributing): add instructions on keeping fork up to date with …
c8a5d07 
…upstream repo (#436)

Included a note before the push section, sayng that contributors may need to sync their changes upstream before pushing to the repository, and linked to the GitHub docs for syncing a fork.

Solves #340.
@dkundel
Copy link
Member

dkundel commented Oct 5, 2019

Thanks for the contribution!

@dkundel dkundel closed this as completed Oct 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dkundel @thatrobotdev @gerhynes