Lines Matching refs:your
6 to get your changes incorporated.
12 * Before we can use your code, you must sign the
16 mainly because you own the copyright to your changes, even after your
17 contribution becomes part of our codebase, so we need your permission to use
18 and distribute your code. We also need to be sure of various other
19 things--for instance that you will tell us if you know that your code
21 after you have submitted your code for review and a member has approved it,
22 but you must do it before we can put your code into our codebase.
28 Please get your company to sign this agreement instead if your contribution is
31 * Unless you have a strong reason not to, please assign copyright of your
46 with your idea so that we can help out and possibly guide you. Coordinating
59 * Make sure the history of your branch is clean. (Ab)use `git rebase -i master`
65 * Always trigger Travis CI builds for your changes (hence why working on a
66 branch is important). Push your branch to GitHub so that Travis CI picks it
68 enable Travis CI builds on your end. Wait for a green result.
87 * Be careful of stylistic errors in your code (see below for style guidelines).
89 By keeping your code clean of style issues upfront, you will speed up the
97 diff by typing `git diff <your-branch> master`.
121 * Unless you have a good reason to do otherwise, name your branch `issue-N`
134 --no-commit your-branch`, followed by an edit of `NEWS`, and terminated with a
152 grammar.](http://julipedia.meroh.net/2013/06/readability-mind-your-typos-and-grammar.html)