Lines Matching +full:pull +full:- +full:requests

6 When development is complete, a patch set should be submitted via GitHub pull requests. A review of…
8 …pull request. Patches sent privately to Maintainers and Committers will not be considered. Because…
25  *     http://www.apache.org/licenses/LICENSE-2.0
35 …-wide notice ("Copyright JS Foundation and other contributors, http://js.foundation") is not permi…
39 …-off is a simple line at the end of the commit message of the patch, which certifies that you wrot…
41 We have the same requirements for using the signed-off-by process as the Linux kernel.
42 In short, you need to include a signed-off-by tag in every patch.
46 > JerryScript-DCO-1.0-Signed-off-by: Random J Developer random@developer.example.org
48 "JerryScript-DCO-1.0-Signed-off-by:" this is a developer's certification that he or she has the rig…
50 ### 4. Open a GitHub [pull request](https://github.com/jerryscript-project/jerryscript/pulls)
52 You can find instructions about opening a pull request [here](https://help.github.com/articles/crea…
69 Changes are submitted via pull requests and only the Maintainers and Committers should approve or r…
72 ## Tips on GitHub Pull Requests
77 * Pull in upstream changes often to stay up-to-date so that when you submit your pull request, merg…
79 For more details, see the GitHub [fork syncing](https://help.github.com/articles/syncing-a-fork) gu…
95 	if "Signed-off-by" not in content:
96 		f.write("\n\nJerryScript-DCO-1.0-Signed-off-by: <Your Name> <Your Email>\n%s" % content)
101 Please refer [Git Hooks](http://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks) for more informat…