blob: b719fc3ca2da77e51f08b2ab84b35281bca86938 [file] [log] [blame] [view]
James E. King III49271792019-01-28 08:32:47 -05001### Pull Request Guidance ###
James E. King III85db0fe2018-04-06 08:37:11 -04002
James E. King III49271792019-01-28 08:32:47 -05003Review the following items to ensure a smooth pull request experience.
James E. King, III8a6d9f42018-04-09 08:11:38 -04004
James E. King III49271792019-01-28 08:32:47 -05005- [ ] Did you make a breaking change? If so:
6
7 - [ ] Add (or reference) an [Apache Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) THRIFT ticket.
8 - [ ] Add a `Breaking-Change` label to the Jira ticket.
9 - [ ] Add a note to the `lib/<language>/README.md` file.
10 - [ ] Add a line to the `CHANGES.md` file.
11
12- [ ] Is this change significant enough to be in release notes?
13
14 All release-note worthy changes require an [Apache Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) THRIFT ticket.
15 For example:
16 - Breaking Changes
17 - New, Deprecated, or Removed Languages
18 - Security Fix
19 - Significant Refactoring
20
21- [ ] If there is an [Apache Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) ticket:
22
23 - [ ] Is the [Apache Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) THRIFT ticket identifier in the PR title?
James E. King III85db0fe2018-04-06 08:37:11 -040024
25 THRIFT-9999: an example pull request title
26
James E. King III49271792019-01-28 08:32:47 -050027 - [ ] Is the [Apache Jira](https://issues.apache.org/jira/projects/THRIFT/issues/) THRIFT ticket identifier and affected languages in the commit message?
James E. King III85db0fe2018-04-06 08:37:11 -040028
29 THRIFT-9999: [summary of fix, one line if possible]
30 Client: [language(s) affected, comma separated, use lib/ directory names please]
31
James E. King III49271792019-01-28 08:32:47 -050032- [ ] Did you squash your changes to a single commit?
33
34 Committers can squash when they merge, but sometimes we forget, and it makes the history
35 pretty dirty. Please squash your pull requests to a single commit if you can.
36
James E. King III10cfd6a2018-04-06 08:43:04 -040037For more information about committing, see CONTRIBUTING.md