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

Add pull request template #226

Merged
merged 1 commit into from Oct 23, 2018
Merged

Add pull request template #226

merged 1 commit into from Oct 23, 2018

Conversation

starryeyez024
Copy link
Member

No description provided.

Copy link
Contributor

@kylebuch8 kylebuch8 left a comment

Choose a reason for hiding this comment

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

Laggy Graphics? Try Mac.

@kylebuch8 kylebuch8 merged commit 25db7a8 into master Oct 23, 2018
@kylebuch8 kylebuch8 deleted the pull-request-templates branch October 23, 2018 16:40
@mwcz
Copy link
Contributor

mwcz commented Oct 24, 2018

Haha!

### Ready-for-merge Checklist

- [ ] Expected files: all files in the merge request related to one feature request?
- [ ] Is your branch up-to-date with the master branch?
Copy link
Contributor

Choose a reason for hiding this comment

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

This is automated, so I think we can get by without asking it directly. Branches cannot be merged if they aren't up to date, and github offers an "Update" button to do the update. The UI makes it clear that this is necessary.

Copy link
Member Author

Choose a reason for hiding this comment

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

@mwcz ack, i'll update that too, i need to rename the file to get github to "see" it


- [ ] Expected files: all files in the merge request related to one feature request?
- [ ] Is your branch up-to-date with the master branch?
- [ ] Did automated tests pass?
Copy link
Contributor

Choose a reason for hiding this comment

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

This is also automated, PRs cannot be merged unless tests are passing. I think we can get by without asking this directly as well, since UI answers it for us.

- [ ] Did automated tests pass?
- [ ] Was it [browser-tested](https://docs.google.com/spreadsheets/d/1luriPYswlGcKdcbKhQfW6kxIgj7tjNjnBVP7yZ4onwA/edit#gid=1660273076)?
- [ ] Was this feature demo'd and the design review task marked as complete?
- [ ] Did it get a LGTM *after the last commit*? (changelog updates are exempt from this rule)
Copy link
Contributor

Choose a reason for hiding this comment

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

We can make this automated in the repo's merging settings, sounds like a really good idea to me.

Copy link
Member Author

Choose a reason for hiding this comment

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

sweet, should i leave this checkbox in place until we automate it?

Copy link
Member Author

Choose a reason for hiding this comment

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

@mwcz ^

Copy link
Contributor

Choose a reason for hiding this comment

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

@starryeyez024 Sorry for the delay! I already turned it on, so you can remove the checkbox. :)

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.

None yet

3 participants