Searched +full:pull +full:- +full:requests (Results 1 – 25 of 1081) sorted by relevance
12345678910>>...44
| /external/grpc-grpc/ |
| D | CONTRIBUTING_STEPS.md | 1 # Contributing to gRPC: A Step-By-Step Guide
10 …[active GitHub account](https://docs.github.com/en/get-started/quickstart/creating-an-account-on-g…
11 1. [An understanding of Git and GitHub](https://docs.github.com/en/get-started/using-git/about-git)
13 resolve, push, pull, fetch
14 etc.](https://docs.github.com/en/get-started/using-git/about-git)
15 1. [git installed and working on your machine](https://github.com/git-guides/install-git)
17 Objective-C, PHP, or C#.
21 The GitHub repository for the C-based gRPC (C++, Python, Ruby, Objective-C, PHP, C#)
30 [own fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-f…
33 … 
[all …]
|
| /external/pytorch/.github/workflows/ |
| D | stale.yml | 3 # Compared to actions/stale, it is implemented to make API requests proportional
9 # - If a PR is not labeled stale, after 60 days inactivity label the PR as stale and comment about …
10 # - If a PR is labeled stale, after 30 days inactivity close the PR.
11 # - `high priority` and `no-stale` PRs are exempt.
13 name: Close stale pull requests
18 - cron: 30 * * * *
24 runs-on: linux.large
27 pull-requests: write
30 - uses: actions/github-script@v6
33 // Do some dumb retries on requests.
[all …]
|
| /external/aws-crt-java/ |
| D | CONTRIBUTING.md | 6 Please read through this document before submitting any issues or pull requests to ensure we have a…
10 ## Reporting Bugs/Feature Requests
14 …ng open](https://github.com/awslabs/aws-crt-java/issues), or [recently closed](https://github.com/…
23 ## Contributing via Pull Requests
24 Contributions via pull requests are much appreciated. Before sending us a pull request, please ensu…
27 2. You check existing open, and recently merged, pull requests to make sure someone else hasn't add…
28 3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
30 To send us a pull request, please:
36 5. Send us a pull request, answering any default questions in the pull request interface.
37 6. Wait for a repository collaborator to look at your pull request, run the automated tests, and re…
[all …]
|
| /external/python/bumble/docs/mkdocs/src/development/ |
| D | contributing.md | 4 …Pull Request (a.k.a PR). Please familiarize yourself with how that works (see [GitHub Pull Request…
6 You should follow the project's [code style](code_style.md), and pre-check your code before submitt…
7 …lly: running the tests, the linter, and the formatter), use the `project.pre-commit` `invoke` comm…
10 $ invoke project.pre-commit
|
| /external/aws-sdk-java-v2/ |
| D | CONTRIBUTING.md | 5 bug reports, feature requests, and code contributions.
8 * [Bug Reports](#bug-reports)
9 * [Feature Requests](#feature-requests)
10 * [Code Contributions](#code-contributions)
11 * [Additional Resources](#additional-resources)
14 Bug reports are accepted through the [this][bug-report] page.
16 The following labels are used to track bug related issues: [Bug][label-bug],
17 [Documentation Issue][label-doc-issue].
53 ## Feature Requests
54 Feature requests are submitted through the [this][feature-request] page.
[all …]
|
| /external/json-schema-validator/src/test/suite/ |
| D | CONTRIBUTING.md | 5 Both pull requests *and* reviews are welcome from any and all, regardless of their "formal" relatio…
14 ## Reviewing a Pull Request
16 Pull requests may (and often should) be reviewed for approval by a single reviewer whose job it is …
18 Other contributors are also encouraged to comment on pull requests whenever they have feedback, eve…
20 If additional reviewers have participated in a pull request, the submitter should not rely on a sin…
23 …xplicitly is currently not needed, as the entire review team is generally pinged for pull requests.
24 … choose to do so if they want specific review from an individual, or if a pull request is sitting …
25 For the latter scenario, leaving a comment on the pull request or in Slack is also reasonable.
27 Confirming that a pull request runs successfully on an implementation is *not* generally sufficient…
34 Reviewing pull requests is an extremely valuable contribution!
[all …]
|
| /external/guava/ |
| D | CONTRIBUTING.md | 8 2. Pull requests are great for small fixes for bugs, documentation, etc.
9 3. Pull requests are not merged directly into the master branch.
13 -----------
27 Pull requests
28 -------------
36 Some examples of types of pull requests that are immediately helpful:
38 - Fixing a bug without changing a public API.
39 - Fixing or improving documentation.
40 - Improvements to Maven configuration.
52 done using `git rebase -i`). Do your best to have a
[all …]
|
| /external/python/httplib2/ |
| D | CHANGELOG | 3 explicit build-backend workaround for pip build isolation bug
9 IMPORTANT security vulnerability CWE-93 CRLF injection
17 https://github.com/httplib2/httplib2/pull/168
22 https://github.com/httplib2/httplib2/pull/163
53 https://github.com/httplib2/httplib2/pull/150
56 https://github.com/httplib2/httplib2/pull/143
59 https://github.com/httplib2/httplib2/pull/149
64 https://github.com/httplib2/httplib2/pull/145
69 https://github.com/httplib2/httplib2/pull/140
74 https://github.com/httplib2/httplib2/pull/138
[all …]
|
| /external/executorch/.github/ |
| D | pull_request_template.md | 2 …EMOVE] See [CONTRIBUTING.md's Pull Requests](https://github.com/pytorch/executorch/blob/main/CONTR…
4 [PLEASE REMOVE] If this PR closes an issue, please add a `Fixes #<issue-id>` line.
6 … check out [CONTRIBUTING.md's Pull Requests](https://github.com/pytorch/executorch/blob/main/CONTR…
|
| /external/curl/docs/ |
| D | CONTRIBUTE.md | 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 10 of them - or 9
104 the most up-to-date sources from the git repository, but the latest release
136 Ideally you file a [pull request on
[all …]
|
| /external/pytorch/docs/source/community/ |
| D | contribution_guide.rst | 3 …Contribution Guide <https://github.com/pytorch/pytorch/wiki/The-Ultimate-Guide-to-PyTorch-Contribu…
8 PyTorch is a GPU-accelerated Python tensor computation package for
9 building deep neural networks using a tape-based autograd systems.
15 --------------------
28 - **Figure out what you're going to work on.** The majority of open
34 - Look through the `issue
41 - Join us on `dev discuss <https://dev-discuss.pytorch.org/>`_
46 - **Figure out the scope of your change and reach out for design
47 comments on a GitHub issue if it's large.** The majority of pull
48 requests are small; in that case, no need to let us know about what
[all …]
|
| /external/protobuf/ |
| D | CONTRIBUTING.md | 31 We accept patches in the form of github pull requests. If you are new to
32 github, please read [How to create github pull requests](https://help.github.com/articles/about-pul…
43 … need to sign an [individual CLA](https://cla.developers.google.com/about/google-individual?csw=1).
45 …then you'll need to sign a [corporate CLA](https://cla.developers.google.com/about/google-corporat…
50 Before sending out your pull request, please familiarize yourself with the
56 Most pull requests should go to the main branch and the change will be
59 already merged to main, and then create a pull request cherry-picking the
62 For each pull request, a protobuf team member will be assigned to review the
63 pull request. For minor cleanups, the pull request may be merged right away
66 our response time within 7-days but if you don’t get any response in a few
[all …]
|
| /external/cronet/stable/third_party/protobuf/ |
| D | CONTRIBUTING.md | 31 We accept patches in the form of github pull requests. If you are new to
32 github, please read [How to create github pull requests](https://help.github.com/articles/about-pul…
43 … need to sign an [individual CLA](https://cla.developers.google.com/about/google-individual?csw=1).
45 …then you'll need to sign a [corporate CLA](https://cla.developers.google.com/about/google-corporat…
50 Before sending out your pull request, please familiarize yourself with the
56 Most pull requests should go to the main branch and the change will be
59 already merged to main, and then create a pull request cherry-picking the
62 For each pull request, a protobuf team member will be assigned to review the
63 pull request. For minor cleanups, the pull request may be merged right away
66 our response time within 7-days but if you don’t get any response in a few
[all …]
|
| /external/cronet/tot/third_party/protobuf/ |
| D | CONTRIBUTING.md | 31 We accept patches in the form of github pull requests. If you are new to
32 github, please read [How to create github pull requests](https://help.github.com/articles/about-pul…
43 … need to sign an [individual CLA](https://cla.developers.google.com/about/google-individual?csw=1).
45 …then you'll need to sign a [corporate CLA](https://cla.developers.google.com/about/google-corporat…
50 Before sending out your pull request, please familiarize yourself with the
56 Most pull requests should go to the main branch and the change will be
59 already merged to main, and then create a pull request cherry-picking the
62 For each pull request, a protobuf team member will be assigned to review the
63 pull request. For minor cleanups, the pull request may be merged right away
66 our response time within 7-days but if you don’t get any response in a few
[all …]
|
| /external/MPAndroidChart/ |
| D | CONTRIBUTING.md | 10 Bug-fixes and features often come from users of the MPAndroidChart library and improve it greatly. …
14 There are two main issue templates, one for bugs and another for feature requests. Please use them!…
18 ## Making Pull Requests
20 Careful! If you fail to follow these guidlines, you're pull request may be closed, *even if it's re…
22 …arch** open [pull requests] AND existing [issues] to make sure what you want to do isn't already b…
25 1. **Add** your commits, they MUST follow the [Commit Style](#commit-style) below
27 1. **Create** a pull request, following the auto-generated template
33 …[#3975](https://github.com/PhilJay/MPAndroidChart/pull/3975) for an example of a good-made-better …
44 …You may prefer [Tim Pope's style], you might like the [commitizen-friendly] way. Regardless of the…
49 changes more thoroughly. If the change is obvious and self-explanatory
[all …]
|
| /external/rust/android-crates-io/crates/miette/ |
| D | CONTRIBUTING.md | 7 * [Request Support](#request-support)
8 * [Report an Error or Bug](#report-an-error-or-bug)
9 * [Request a Feature](#request-a-feature)
11 * [Project Setup](#project-setup)
12 * [Contribute Documentation](#contribute-documentation)
13 * [Contribute Code](#contribute-code)
15 * [Provide Support on Issues](#provide-support-on-issues)
16 * [Label Issues](#label-issues)
17 * [Clean Up Issues and PRs](#clean-up-issues-and-prs)
18 * [Review Pull Requests](#review-pull-requests)
[all …]
|
| /external/rust/android-crates-io/crates/tinytemplate/ |
| D | CONTRIBUTING.md | 7 Issues, ideas, requests and questions should be posted on the issue tracker at:
13 Pull requests are welcome, though please raise an issue or post a comment for discussion first. We'…
19 `git clone git@github.com:your-username/TinyTemplate.git`
30 rustup component add clippy-preview
37 rustup component add rustfmt-preview
41 …'re finished, push to your fork and submit a pull request. We try to respond to new issues and pul…
43 Some things that will increase the chance that your pull request is accepted:
49 … is one of the core goals of the TinyTemplate project, so new code in pull requests should have cl…
55 - Beginner - Suitable for people new to TinyTemplate
56 - Intermediate - More challenging, likely involves some non-obvious design decisions or knowledge o…
[all …]
|
| /external/vulkan-validation-layers/ |
| D | GOVERNANCE.md | 6 …- The goal is for validation layer behavior to enforce the vulkan specification on applications. Q…
8 - [Core Specification](https://www.khronos.org/registry/vulkan/specs/1.0/html/vkspec.html)
9 - [Header Files](https://www.khronos.org/registry/vulkan/#headers)
10 - [SDK Resources](https://vulkan.lunarg.com)
12 - Updates of validation layer functionality should be available in a timely fashion
13 - Every effort will be made to be responsive to ISV issues with validation layers
15 - Google and LunarG collaboration:
16 - Google: Monitor for Android
17 - LunarG: Monitor for desktop (Windows and Linux)
18 …- Continuous Integration: HW test farms operated by Google and LunarG monitor various hardware/sof…
[all …]
|
| /external/threetenbp/ |
| D | README.md | 3 JSR-310 provides a new date and time library for Java SE 8.
8 The backport is NOT an implementation of JSR-310, as that would require
11 use the JSR-310 API on Java SE 6 and 7.
14 Active development on JSR-310 is at [OpenJDK](http://openjdk.java.net/):
16 This GitHub repository is a fork of that originally used to create JSR-310.
17 That repository used the same BSD-3-Clause license as this repository.
20 Pull requests and issues will only be considered so far as matching the behaviour
26 #### Time-zone data
27 The time-zone database is stored as a pre-compiled dat file that is included in the built jar.
28 The version of the time-zone data used is stored within the dat file (near the start).
[all …]
|
| /external/rust/android-crates-io/crates/criterion/ |
| D | CONTRIBUTING.md | 7 Issues, ideas, requests and questions should be posted on the issue tracker at:
13 Criterion.<span></span>rs does not accept pull requests to update dependencies unless specifically
19 Pull requests are welcome, though please raise an issue for discussion first if none exists. We're …
25 `git clone git@github.com:your-username/criterion.rs.git`
32 cargo test --all
39 rustup component add clippy-preview
40 cargo clippy --all
46 rustup component add rustfmt-preview
47 cargo fmt --all
50 …'re finished, push to your fork and submit a pull request. We try to respond to new issues and pul…
[all …]
|
| /external/rust/android-crates-io/crates/criterion-plot/ |
| D | CONTRIBUTING.md | 7 Issues, ideas, requests and questions should be posted on the issue tracker at:
13 Criterion.<span></span>rs does not accept pull requests to update dependencies unless specifically
19 Pull requests are welcome, though please raise an issue for discussion first if none exists. We're …
25 `git clone git@github.com:your-username/criterion.rs.git`
32 cargo test --all
39 rustup component add clippy-preview
40 cargo clippy --all
46 rustup component add rustfmt-preview
47 cargo fmt --all
50 …'re finished, push to your fork and submit a pull request. We try to respond to new issues and pul…
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/iron-form/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
32 The `paper-foo` element causes the page to turn pink when clicked.
44 1. Put a `paper-foo` element in the page.
46 3. Click the `paper-foo` element.
53 ### Submitting Pull Requests
55 …pull request**, please ensure that an issue exists for the corresponding change in the pull reques…
57 When submitting pull requests, please provide:
59 …ing issue** or issues that will be closed by the pull request. Please refer to these issues in the…
72 …emoving styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/iron-location/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
32 The `paper-foo` element causes the page to turn pink when clicked.
44 1. Put a `paper-foo` element in the page.
46 3. Click the `paper-foo` element.
53 ### Submitting Pull Requests
55 …pull request**, please ensure that an issue exists for the corresponding change in the pull reques…
57 When submitting pull requests, please provide:
59 …ing issue** or issues that will be closed by the pull request. Please refer to these issues in the…
72 …emoving styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/iron-checked-element-behavior/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
32 The `paper-foo` element causes the page to turn pink when clicked.
44 1. Put a `paper-foo` element in the page.
46 3. Click the `paper-foo` element.
53 ### Submitting Pull Requests
55 …pull request**, please ensure that an issue exists for the corresponding change in the pull reques…
57 When submitting pull requests, please provide:
59 …ing issue** or issues that will be closed by the pull request. Please refer to these issues in the…
72 …emoving styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/paper-menu/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
32 The `paper-foo` element causes the page to turn pink when clicked.
44 1. Put a `paper-foo` element in the page.
46 3. Click the `paper-foo` element.
53 ### Submitting Pull Requests
55 …pull request**, please ensure that an issue exists for the corresponding change in the pull reques…
57 When submitting pull requests, please provide:
59 …ing issue** or issues that will be closed by the pull request. Please refer to these issues in the…
72 …emoving styles that leaked which would cause the page to turn pink whenever `paper-foo` is clicked.
[all …]
|
12345678910>>...44