Lines Matching +full:pull +full:- +full:requests
1 <!--
4 SPDX-License-Identifier: curl
5 -->
28 notified of pull requests and new issues posted there.
60 [curl-library mailing list](https://curl.se/mail/list.cgi?list=curl-library)
69 [CODE_STYLE](https://curl.se/dev/code-style.html) already established in
75 ### Non-clobbering All Over
87 odd problems, but discussions and opinions do not agree with 510 of them - or
104 the most up-to-date sources from the git repository, but the latest release
136 Ideally you file a [pull request on
138 patch to [the curl-library mailing
139 list](https://curl.se/mail/list.cgi?list=curl-library).
142 it into a pull request for you, to have the CI jobs verify it proper before it
156 ### About pull requests
158 With GitHub it is easy to send a [pull
162 We strongly prefer pull requests to mailed patches, as it makes it a proper
167 Every pull request submitted is automatically tested in several different
173 try to update your pull requests to rerun the tests later as described below.
175 You can update your pull requests by pushing new commits or force-pushing
176 changes to existing commits. Force-pushing an amended commit without any
179 When you adjust your pull requests after review, consider squashing the
182 A pull request sent to the project might get labeled `needs-votes` by a
184 checks and qualifications this pull request must also receive more "votes" of
186 form of messages saying so, or thumbs-up reactions on GitHub.
194 to the list or better yet: change it to a pull request.
200 ---- start ----
202 -- empty line --
207 -- empty line --
208 [[0] URL - Reference to a URL in the description, almost like Markdown;
209 the last numbered reference is followed by an -- empty line -- ]
210 [Follow-up to {shorthash} - if this fixes or continues a previous commit;
212 followed by an -- empty line -- ]
215 [Approved-by: John Doe - credit someone who approved the PR; if you are
216 committing this for someone else using --author=... you do not need this
218 [Authored-by: John Doe - credit the original author of the code; only use
219 this if you cannot use "git commit --author=..."]
220 [Signed-off-by: John Doe - we do not use this, but do not bother removing it]
221 [whatever-else-by: credit all helpers, finders, doers; try to use one of
223 Acked-by:, Assisted-by:, Co-authored-by:, Found-by:, Reported-by:,
224 Reviewed-by:, Suggested-by:, Tested-by:]
225 [Ref: #1234 - if this is related to a GitHub issue or PR, possibly one that
229 [Fixes #1234 - if this closes a GitHub issue; GitHub closes the issue once
231 [Closes #1234 - if this closes a GitHub PR; GitHub closes the PR once this
233 ---- stop ----
237 - use the imperative, present tense: "change" not "changed" nor "changes"
238 - do not capitalize the first letter
239 - no period (.) at the end
245 Do not forget to use commit --author=... if you commit someone else's work, and
251 are using --author=... which hides your identity. Do not include people's
259 repo instead of sending changes as pull requests or by mail as patches.
281 git format-patch remotes/origin/master
283 This creates files in your local directory named `NNNN-[name].patch` for each
286 Now send those patches off to the curl-library list. You can of course opt to
287 do that with the 'git send-email' command.
297 diff -u unmodified-file.c my-changed-one.c > my-fixes.diff
302 diff -ur curl-original-dir curl-modified-sources-dir > my-fixes.diff
308 - [Webinar on getting code into cURL](https://www.youtube.com/watch?v=QmZ3W1d6LQI)
312 There is a CI job called **REUSE compliance / check** that runs on every pull
318 the SPDX-License-Identifier included. If the header does not work, you can use a