Lines Matching full:to
1 # How to Contribute #
3 …to the Apache Thrift project! Information on why and how to contribute is available on the Apache…
12 it activates the continuous integration (CI) build systems at Appveyor and Travis to build your cha…
18 1. All pull requests should contain a single commit per issue, or we will ask you to squash it.
31 1. Clone the fork to your development system.
33 1. Modify the source to include the improvement/bugfix, and:
35 * Remember to provide *tests* for all submitted changes!
38 …to [Travis CI](http://docs.travis-ci.com/user/getting-started/#Step-one%3A-Sign-in) and [AppVeyor]…
40 1. Squash your changes to a single commit. This maintains clean change history.
41 …1. Commit and push changes to your branch (please use issue name and description as commit title, …
42 …1. Use GitHub to create a pull request going from your branch to apache:master. Ensure that the J…
43 …1. Wait for other contributors or committers to review your new addition, and for a CI build to co…
44 …1. Wait for a committer to commit your patch. You can nudge the committers if necessary by sendin…
46 ## If you want to build the project locally ##
54 ## If you want to review open issues... ##
56 …itHub Pull Request Backlog](https://github.com/apache/thrift/pulls). Code reviews are open to all.
57 …ssues.apache.org/jira/browse/THRIFT). You can search for tickets relating to languages you are in…
61 …1. Check to see if the issue is already in the [Jira issue tracker](http://issues.apache.org/jira/…
67 To create a patch from changes in your local directory:
71 …ntributors or committers to review your changes, and then for a committer to apply your patch. Th…
75 Sometimes commmitters may ask you to take actions in your pull requests. Here are some recipes tha…
79 …t rebased your existing pull request, you can squash all your commits down to a single commit. Th…
81 1. Use the command ``git log`` to identify how many commits you made since you began.
84 4. Change all other lines from "pull" to "fixup".
87 If you already have a pull request outstanding, you will need to do a "force push" to overwrite it …
95 If your pull request has a conflict with master, it needs to be rebased:
104 …ns commits that are not yours, then you should use the following technique to fix the bad merge in…
111 squash your changes to a single commit if there is more than one (see above)
114 …is procedure will apply only your commits in order to the current master, then you will squash the…