Skip to content
This repository has been archived by the owner on Jan 10, 2018. It is now read-only.

Pull request template #276

Merged
merged 4 commits into from Oct 14, 2016
Merged

Conversation

josephfusco
Copy link
Collaborator

Adds a pull request template to the GitHub project.

See GitHub article: https://help.github.com/articles/creating-a-pull-request-template-for-your-repository/

This doesn't fix #271 but supports it.

@samikeijonen
Copy link
Contributor

samikeijonen commented Oct 13, 2016

+1. I'd also need helpful text how to sync your local master branch with remote branch. And how to use rebase for custom PR branch after that. Or is that even suggested workflow.

@grappler
Copy link
Member

@samikeijonen See this #90 (comment)

- [ ] Are all the above sections filled out appropriately?
- [ ] Have you read [CONTRIBUTING.md](https://github.com/WordPress/twentyseventeen/blob/master/CONTRIBUTING.md)?
- [ ] Did you maintain a new line at the end of each file modified/added?
- [ ] If this adds new js dependencies, did you add them to [.jscrc](https://github.com/josephfusco/twentyseventeen/blob/master/.jscsrc) & [.jshintignore](https://github.com/WordPress/twentyseventeen/blob/master/.jshintignore)?
Copy link
Contributor

@enodekciw enodekciw Oct 13, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Both [.jscsrc] and [.jsintignore] should be linked to WordPress/twentyseventeen

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@enodekciw good catch 👍

@samikeijonen
Copy link
Contributor

Thanks @grappler for tip. First step (syncing master branch from this master branch) is crystal clear.

But I'm confused of command git reset --hard master after checking out on my svg branch. Wouldn't that make my svg branch exactly the same as master branch. And I would lose all the modifications I made on svg branch.

Shouldn't I use git rebase master command instead and try to solve merge conflicts manually?

@mor10
Copy link
Contributor

mor10 commented Oct 14, 2016

@samikeijonen When I work on non-WP projects, we typically use a process like the one outlined in this article: https://github.com/edx/edx-platform/wiki/How-to-Rebase-a-Pull-Request

I have no idea if this is what the team is looking for, but it's a pretty clean and straight-forward process:

// Checkout master:
git checkout master
// Get the updates:
git pull --rebase upstream master
// Checkout your working feature branch:
git checkout [working branch]
// Rebase updates to the branch:
git rebase master
// resolve and commit conflicts (happens in editor context)
// Force the changes to the remote branch (pull request):
git push --force

If this is not a desirable methodology, please let me know.

@samikeijonen
Copy link
Contributor

samikeijonen commented Oct 14, 2016

Thanks @mor10. That's pretty much the workflow I'm using also. But instead of git pull --rebase upstream master I sync the master branch like outlined in this article.

In #206 I probably used merge and messed PR. I'll try rebase this time in #253. Fingers crossed.

@melchoyce melchoyce merged commit 87bf749 into WordPress:master Oct 14, 2016
@josephfusco josephfusco deleted the pull-request-template branch October 18, 2016 14:41
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Add rebase and line endings docs to CONTRIBUTING.md
6 participants