Lines Matching full:for
3 Thank you for your interest in contributing to the Apache Thrift project! Information on why and h…
14 for a successful pull request:
19 …itle must begin with the Jira THRIFT ticket identifier if it has an associated ticket, for example:
23 1. Commit messages must follow this pattern for code changes (deviations will not be merged):
26 Client: [language(s) affected, comma separated, for example: "cpp,erl,perl"]
32 1. Create a branch for your changes (best practice is issue as branch name, e.g. THRIFT-9999).
35 * Remember to provide *tests* for all submitted changes!
37 …/docs/coding_standards) (you can run 'make style', which ensures proper format for some languages).
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…
48 For Windows systems, see our detailed instructions on the [CMake README](/build/cmake/README.md).
50 For Windows Native C++ builds, see our detailed instructions on the [WinCPP README](/build/wincpp/R…
52 For unix systems, see our detailed instructions on the [Docker README](/build/docker/README.md).
57 …n search for tickets relating to languages you are interested in or currently using with thrift, f…
71 …for contributors or committers to review your changes, and then for a committer to apply your patc…
73 ## GitHub recipes for Pull Requests ##
79 …n squash all your commits down to a single commit. This makes life easier for the committers. If…