Skip to content

NONE: Clarify pull request rules#11

Open
wyrzyk wants to merge 1 commit intoatlassian:masterfrom
wyrzyk:issue/NONE-clarify-pull-request-rules
Open

NONE: Clarify pull request rules#11
wyrzyk wants to merge 1 commit intoatlassian:masterfrom
wyrzyk:issue/NONE-clarify-pull-request-rules

Conversation

@wyrzyk
Copy link
Copy Markdown
Contributor

@wyrzyk wyrzyk commented Feb 13, 2020

No description provided.

@wyrzyk wyrzyk requested a review from a team February 13, 2020 07:29

## Getting Your Pull Request Merged

All Pull Requests must be approved by at least one member of the @atlassian/jpt team
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This is already explained and enforced by GitHub GUI.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I usually read CONTRIBUTING.md before I start to write a code. GUI explains rules at the last phase of the contribution.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

You can read CODEOWNERS before writing code too. IMHO it's a micro-value, not worth denormalizing


### Pull Request Readiness readiness checklist

* [ ] Includes tests to exercise the new behavior and bugs.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Are these checkboxes supposed to be ticked? They're not tickable.
If we want to create a literal PR checklist, we can use a PR template.

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.

2 participants