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

Feature: Allow a configuration setting to set a markdown template for pull requests #937

Closed
dhilton opened this issue Jun 30, 2015 · 4 comments

Comments

@dhilton
Copy link

dhilton commented Jun 30, 2015

It would be great if on a global basis, I could set a text based template for pull requests, so that when I issue a pull request it gives me a set of headings to fill in, ensuring that I meet the given style for PR's.

References:

http://www.annashipman.co.uk/jfdi/good-pull-requests.html
https://github.com/alphagov/styleguides/blob/master/pull-requests.md

Happy to take a first stab at this improvement if committers like the cut of it's jib.

@hasit
Copy link

hasit commented Jun 30, 2015

I can see this being very useful. Some projects can provide templates if they are strict about their format and hub can read it from .git or a special directory inside.
👍

@mislav
Copy link
Owner

mislav commented Sep 27, 2015

Note that the --edit option was proposed to be added to hub pull-request that will allow passing of filename and editing it in text editor in the same step: #924

@dhilton
Copy link
Author

dhilton commented Oct 20, 2015

@mislav - I'll have a crack at adding tests to #924 - that looks ok as long as we can cleanly rebase against current master.

@paul
Copy link

paul commented Dec 14, 2015

I'm also 👍 on this feature request. Git already has a template system for commit messages ( https://robots.thoughtbot.com/better-commit-messages-with-a-gitmessage-template ), so something similar for pull request templates would be extremely helpful.

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

No branches or pull requests

4 participants