Lines Matching +full:pull +full:- +full:requests
22 notified of pull requests and new issues posted there.
54 the [curl-library mailing
55 list](https://curl.se/mail/list.cgi?list=curl-library) will give you a
63 [CODE_STYLE](https://curl.se/dev/code-style.html) already established in
69 ### Non-clobbering All Over
81 odd problems, but discussions and opinions do not agree with 510 of them - or
98 the most up-to-date sources from the git repository, but the latest release
129 Ideally you file a [pull request on
131 patch to [the curl-library mailing
132 list](https://curl.se/mail/list.cgi?list=curl-library).
135 convert it into a pull request for you, to have the CI jobs verify it proper
149 ### About pull requests
151 With GitHub it is easy to send a [pull
155 We strongly prefer pull requests to mailed patches, as it makes it a proper
160 Every pull request submitted will automatically be tested in several different
166 try to update your pull requests to rerun the tests later as described below.
168 You can update your pull requests by pushing new commits or force-pushing
169 changes to existing commits. Force-pushing an amended commit without any
172 When you adjust your pull requests after review, consider squashing the
175 A pull request sent to the project might get labeled `needs-votes` by a
177 checks and qualifications this pull request must also receive more "votes" of
179 form of messages saying so, or thumbs-up reactions on GitHub.
187 to the list or better yet: change it to a pull request.
193 ---- start ----
195 -- empty line --
200 -- empty line --
201 [[0] URL - Reference to a URL in the description, almost like Markdown;
202 the last numbered reference is followed by an -- empty line -- ]
203 [Follow-up to {shorthash} - if this fixes or continues a previous commit;
205 followed by an -- empty line -- ]
208 [Approved-by: John Doe - credit someone who approved the PR; if you are
209 committing this for someone else using --author=... you do not need this
211 [Authored-by: John Doe - credit the original author of the code; only use
212 this if you cannot use "git commit --author=..."]
213 [Signed-off-by: John Doe - we do not use this, but do not bother removing it]
214 [whatever-else-by: credit all helpers, finders, doers; try to use one of
216 Acked-by:, Assisted-by:, Co-authored-by:, Found-by:, Reported-by:,
217 Reviewed-by:, Suggested-by:, Tested-by:]
218 [Ref: #1234 - if this is related to a GitHub issue or PR, possibly one that
222 [Fixes #1234 - if this closes a GitHub issue; GitHub will actually
224 [Closes #1234 - if this closes a GitHub PR; GitHub will actually
226 ---- stop ----
230 - use the imperative, present tense: "change" not "changed" nor "changes"
231 - do not capitalize the first letter
232 - no period (.) at the end
238 Do not forget to use commit --author=... if you commit someone else's work, and
244 are using --author=... which hides your identity. Do not include people's
252 repo instead of sending changes as pull requests or by mail as patches.
274 git format-patch remotes/origin/master
276 This creates files in your local directory named `NNNN-[name].patch` for each
279 Now send those patches off to the curl-library list. You can of course opt to
280 do that with the 'git send-email' command.
290 diff -u unmodified-file.c my-changed-one.c > my-fixes.diff
295 diff -ur curl-original-dir curl-modified-sources-dir > my-fixes.diff
301 - [Webinar on getting code into cURL](https://www.youtube.com/watch?v=QmZ3W1d6LQI)
306 pull request and commit to verify that the *REUSE state* of all files are
311 the SPDX-License-Identifier included. If the header does not work, you can use a