Searched +full:pull +full:- +full:requests (Results 1 – 25 of 349) sorted by relevance
12345678910>>...14
| /third_party/node/doc/guides/ |
| D | collaborator-guide.md | 5 * [Issues and pull requests](#issues-and-pull-requests)
6 * [Welcoming first-time contributors](#welcoming-first-time-contributors)
7 * [Closing issues and pull requests](#closing-issues-and-pull-requests)
8 * [Author ready pull requests](#author-ready-pull-requests)
9 * [Handling own pull requests](#handling-own-pull-requests)
10 * [Security issues](#managing-security-issues)
11 * [Accepting modifications](#accepting-modifications)
12 * [Code reviews](#code-reviews)
13 * [Consensus seeking](#consensus-seeking)
14 * [Waiting for approvals](#waiting-for-approvals)
[all …]
|
| D | commit-queue.md | 3 > Stability: 1 - Experimental
5 *tl;dr: You can land pull requests by adding the `commit-queue` label to it.*
9 land pull requests by adding the `commit-queue` label to a PR. All
10 checks will run via node-core-utils, and if the pull request is ready to land,
18 From a high-level, the Commit Queue works as follow:
20 1. Collaborators will add `commit-queue` label to pull requests ready to land
21 2. Every five minutes the queue will do the following for each pull request
23 1. Check if the PR also has a `request-ci` label (if it has, skip this PR
27 3. Remove the `commit-queue` label
31 2. Add `commit-queue-failed` label to the PR
[all …]
|
| /third_party/node/ |
| D | CONTRIBUTING.md | 3 * [Code of Conduct](#code-of-conduct)
5 * [Pull Requests](#pull-requests)
6 * [Developer's Certificate of Origin 1.1](#developers-certificate-of-origin)
8 ## [Code of Conduct](./doc/guides/contributing/code-of-conduct.md)
14 See [details on our policy on Code of Conduct](./doc/guides/contributing/code-of-conduct.md).
18 * [Asking for General Help](./doc/guides/contributing/issues.md#asking-for-general-help)
19 * [Discussing non-technical topics](./doc/guides/contributing/issues.md#discussing-non-technical-to…
20 * [Submitting a Bug Report](./doc/guides/contributing/issues.md#submitting-a-bug-report)
21 * [Triaging a Bug Report](./doc/guides/contributing/issues.md#triaging-a-bug-report)
23 ## [Pull Requests](./doc/guides/contributing/pull-requests.md)
[all …]
|
| D | onboarding.md | 9 confirm that they are using [two-factor authentication][]. It will not be
10 possible to add them to the organization if they are not using two-factor
15 * Suggest the new Collaborator install [`node-core-utils`][] and
23 [Who to CC in the issue tracker][who-to-cc].
28 * [local setup](#local-setup)
29 * [project goals and values](#project-goals-and-values)
30 * [managing the issue tracker](#managing-the-issue-tracker)
31 * [reviewing pull requests](#reviewing-pull-requests)
32 * [landing pull requests](#landing-pull-requests)
37 * Make sure you have whitespace=fix: `git config --global --add
[all …]
|
| D | GOVERNANCE.md | 3 <!-- TOC -->
7 * [Collaborator activities](#collaborator-activities)
8 * [Technical steering committee](#technical-steering-committee)
9 * [TSC meetings](#tsc-meetings)
10 * [Collaborator nominations](#collaborator-nominations)
12 * [Consensus seeking process](#consensus-seeking-process)
14 <!-- /TOC -->
18 Triagers assess newly-opened issues in the [nodejs/node][] and [nodejs/help][]
19 repositories. The GitHub team for Node.js triagers is @nodejs/issue-triage.
22 * Ability to label issues and pull requests
[all …]
|
| /third_party/node/doc/guides/contributing/ |
| D | pull-requests.md | 1 # Pull requests
4 * [Setting up your local environment](#setting-up-your-local-environment)
5 * [Step 1: Fork](#step-1-fork)
6 * [Step 2: Branch](#step-2-branch)
7 * [The process of making changes](#the-process-of-making-changes)
8 * [Step 3: Code](#step-3-code)
9 * [Step 4: Commit](#step-4-commit)
10 * [Commit message guidelines](#commit-message-guidelines)
11 * [Step 5: Rebase](#step-5-rebase)
12 * [Step 6: Test](#step-6-test)
[all …]
|
| /third_party/node/test/fixtures/wpt/resources/webidl2/ |
| D | CHANGELOG.md | 3 ## [v10.2.1](https://github.com/w3c/webidl2.js/tree/v10.2.1) (2018-03-09)
6 **Merged pull requests:**
8 - Optimise tokenisation and whitespace skipping [\#139](https://github.com/w3c/webidl2.js/pull/139)…
9 - refactor: small syntax changes [\#137](https://github.com/w3c/webidl2.js/pull/137) ([saschanaz](h…
11 ## [v10.2.0](https://github.com/w3c/webidl2.js/tree/v10.2.0) (2018-01-30)
14 **Merged pull requests:**
16 - Type on union idlType [\#135](https://github.com/w3c/webidl2.js/pull/135) ([saschanaz](https://gi…
17 - feat: add argument/return type [\#134](https://github.com/w3c/webidl2.js/pull/134) ([saschanaz](h…
18 - feat: add dictionary/typedef-type [\#133](https://github.com/w3c/webidl2.js/pull/133) ([saschanaz…
19 - feat: add const-type for idlTypes [\#132](https://github.com/w3c/webidl2.js/pull/132) ([saschana…
[all …]
|
| /third_party/rust/crates/nix/ |
| D | CONTRIBUTING.md | 9 [conduct]: https://www.rust-lang.org/conduct.html
16 [issues]: https://github.com/nix-rust/nix/issues
22 issues][issue-search] to see if there's something related. If not, just
23 [open a new issue][new-issue]!
29 [issue-search]: https://github.com/nix-rust/nix/search?utf8=%E2%9C%93&q=is%3Aissue&type=Issues
30 [new-issue]: https://github.com/nix-rust/nix/issues/new
33 ## Feature / API requests
36 issue][new-issue] requesting it. As with reporting a bug, the more
43 [Rust's issue labeling scheme][rust-labels]:
44 - **A-** prefixed labels state which area of the project the issue
[all …]
|
| /third_party/protobuf/ |
| D | CONTRIBUTING.md | 9 We accept patches in the form of github pull requests. If you are new to
10 github, please read [How to create github pull requests](https://help.github.com/articles/about-pul…
21 … need to sign an [individual CLA](https://cla.developers.google.com/about/google-individual?csw=1).
23 …then you'll need to sign a [corporate CLA](https://cla.developers.google.com/about/google-corporat…
28 Before sending out your pull request, please familiarize yourself with the
34 Most pull requests should go to the master branch and the change will be
37 already merged to master, and then create a pull request cherry-picking the
40 For each pull request, a protobuf team member will be assigned to review the
41 pull request. For minor cleanups, the pull request may be merged right away
44 our response time within 7-days but if you don’t get any response in a few
[all …]
|
| /third_party/rust/crates/tracing/ |
| D | CONTRIBUTING.md | 20 [`CONTRIBUTING.md` file][tokio-contrib] in the `tokio-rs/tokio` repository.
22 [dev]: https://gitter.im/tokio-rs/dev
24 [tokio-contrib]: https://github.com/tokio-rs/tokio/blob/master/CONTRIBUTING.md
31 [coc]: https://github.com/rust-lang/rust/blob/master/CODE_OF_CONDUCT.md
39 tokio-rs/tracing [issue tracker][issues] is the way to report it.
48 often, by opening a Pull Request that changes some bit of something in
54 [issues]: https://github.com/tokio-rs/tracing/issues
67 be presented with a [basic template][issue-template] that should be filled in. If you
83 [issue-template]: .github/ISSUE_TEMPLATE/bug_report.md
106 In the majority of cases, issues are resolved by opening a Pull Request. The
[all …]
|
| /third_party/vulkan-loader/ |
| D | GOVERNANCE.md | 5 - Alignment with the Vulkan Specification and the Loader Specification
6 - [Vulkan Specification](https://github.com/KhronosGroup/Vulkan-Docs)
7 - [Loader Specification](loader/LoaderAndLayerInterface.md)
8 - IHV/ISV Enablement
9 - Updates of loader functionality should be available in a timely fashion
10 - Every effort will be made to be responsive to IHV/ISV issues with the loader
11 - Cross Platform Compatibility
12 - LunarG: Monitor for desktop (Windows and Linux)
13 …- Continuous Integration: HW test farms operated by LunarG monitor various hardware/software platf…
14 - Repo Quality
[all …]
|
| /third_party/skia/third_party/externals/oboe/apps/fxlab/ |
| D | CONTRIBUTING.md | 9 use GitHub pull requests for this purpose. Consult
10 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
11 information on using pull requests.
|
| /third_party/skia/third_party/externals/wuffs/docs/ |
| D | contributing.md | 21 use GitHub pull requests for this purpose. Consult
22 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23 information on using pull requests.
|
| /third_party/skia/third_party/externals/swiftshader/third_party/marl/ |
| D | CONTRIBUTING.md | 21 use GitHub pull requests for this purpose. Consult
22 [GitHub Help](https://help.github.com/articles/about-pull-requests/) for more
23 information on using pull requests.
|
| /third_party/libphonenumber/ |
| D | CONTRIBUTING.md | 5 Please read the following before filing an issue or sending a pull request.
18 [port](http://github.com/google/libphonenumber#third-party-ports),
20 * If you are using the library through a front-end or wrapper, issues
24 group](https://groups.google.com/group/libphonenumber-discuss)? If so, you
30 For acceptable evidence, [see below](#provide-supporting-evidence).
35 * Number type ("fixed-line", "mobile", "short code", etc.):
54 Ideally, change requests for ranges should be accompanied by authoritative
73 * [Corporate CLA](http://developers.google.com/open-source/cla/corporate?csw=1):
84 * [Individual CLA](http://cla.developers.google.com/about/google-individual?csw=1):
97 ## Pull requests
[all …]
|
| D | making-metadata-changes.md | 9 metadata pull requests, but you may use these guidelines to create changes in
11 issue](CONTRIBUTING.md#checklist-before-filing-an-issue) with us.
13 You can read more about the pull request [contribution
14 guidelines](CONTRIBUTING.md#pull-requests).
24 * `resources/ShortNumberMetadata.xml` for short-code data
46 ant -f java/build.xml junit
57 ant -f java/build.xml build-js-metadata
78 ant -f java/build.xml jar
81 Then [run your own demo](run-java-demo.md) and test your changes are as
|
| /third_party/jerryscript/ |
| D | CONTRIBUTING.md | 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)
[all …]
|
| /third_party/libsnd/docs/ |
| D | lists.md | 1 ---
4 ---
9 …tHub issues and pull requests instead](https://docs.github.com/en/free-pro-team@latest/github/coll…
13 - **libsndfile-announce@mega-nerd.com**
14 [Subscribe](mailto:libsndfile-announce-request@mega-nerd.com?subject=subscribe)
17 - **libsndfile-devel@mega-nerd.com**
18 [Subscribe](mailto:libsndfile-devel-request@mega-nerd.com?subject=subscribe)
19 A list for discussing bugs, porting issues and feature requests.
21 - **libsndfile-users@mega-nerd.com**
22 [Subscribe](mailto:libsndfile-users-request@mega-nerd.com?subject=subscribe)
[all …]
|
| /third_party/rust/crates/rust-cexpr/ |
| D | .travis.yml | 3 # This is where pull requests from "bors r+" are built.
4 - staging
5 # This is where pull requests from "bors try" are built.
6 - trying
8 - master
14 - libclang-dev
16 - RUST_BACKTRACE=1 LLVM_CONFIG_PATH=llvm-3.8-config
18 - cargo test --verbose --all
|
| /third_party/cJSON/.github/ |
| D | CONTRIBUTING.md | 4 …e welcome. If you find a bug or want to improve cJSON in another way, pull requests are appreciate…
6 …asted effort, please open an issue to discuss the technical details before creating a pull request.
11 --------
12 …ke pull requests to the `master` branch for small bug- or security fixes (these are usually just a…
15 ------------
35 if ((buffer == NULL) || (buffer->buffer == NULL))
39 buffer_pointer = buffer->buffer + buffer->offset;
41 buffer->offset += strlen((const char*)buffer_pointer);
46 ----------
52 -----------
|
| /third_party/libbpf/ |
| D | .travis.yml | 5 - docker
9 - PROJECT_NAME='libbpf'
10 - AUTHOR_EMAIL="$(git log -1 --pretty=\"%aE\")"
11 - REPO_ROOT="$TRAVIS_BUILD_DIR"
12 - CI_ROOT="$REPO_ROOT/travis-ci"
13 - VMTEST_ROOT="$CI_ROOT/vmtest"
18 - qemu-kvm
19 - zstd
20 - binutils-dev
21 - elfutils
[all …]
|
| /third_party/node/deps/npm/ |
| D | CONTRIBUTING.md | 6 * [Code Structure](#code-structure)
7 * [Running Tests](#running-tests)
11 * [Types of Contributions](#types-of-contributions)
12 * [Contributing an Issue?](#contributing-an-issue)
13 * [Contributing a Question?](#contributing-a-question)
14 * [Contributing a Bug Fix?](#contributing-a-bug-fix)
15 * [Contributing a Feature?](#contributing-a-bug-feature)
16 * [Development Dependencies](#development-dependencies)
21 …munity interaction and contribution. This includes the issue tracker, pull requests, wiki pages, a…
33 │ ├── npm # npm-cli entrypoint for bourne shell
[all …]
|
| /third_party/skia/third_party/externals/swiftshader/third_party/SPIRV-Tools/ |
| D | CONTRIBUTING.md | 1 # Contributing to SPIR-V Tools
5 We organize known future work in GitHub projects. See [Tracking SPIRV-Tools work
7 projects](https://github.com/KhronosGroup/SPIRV-Tools/blob/master/docs/projects.md)
12 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) and
13 [projects](https://github.com/KhronosGroup/SPIRV-Tools/projects). If the bug has
15 [here](https://github.com/KhronosGroup/SPIRV-Tools/issues/new).
21 issue is about. Simply using "Segfault in spirv-opt" is not helpful
30 For feature requests, we use
31 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) as well. Please
40 License Agreement](https://cla-assistant.io/KhronosGroup/SPIRV-Tools) (CLA),
[all …]
|
| /third_party/skia/third_party/externals/spirv-tools/ |
| D | CONTRIBUTING.md | 1 # Contributing to SPIR-V Tools
5 We organize known future work in GitHub projects. See [Tracking SPIRV-Tools work
7 projects](https://github.com/KhronosGroup/SPIRV-Tools/blob/master/docs/projects.md)
12 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) and
13 [projects](https://github.com/KhronosGroup/SPIRV-Tools/projects). If the bug has
15 [here](https://github.com/KhronosGroup/SPIRV-Tools/issues/new).
21 issue is about. Simply using "Segfault in spirv-opt" is not helpful
30 For feature requests, we use
31 [issues](https://github.com/KhronosGroup/SPIRV-Tools/issues) as well. Please
40 License Agreement](https://cla-assistant.io/KhronosGroup/SPIRV-Tools) (CLA),
[all …]
|
| /third_party/node/deps/npm/node_modules/through2/node_modules/readable-stream/ |
| D | GOVERNANCE.md | 5 that is responsible for high-level guidance of the project.
17 [README.md](./README.md#current-project-team-members).
21 The readable-stream GitHub repository is
26 Collaborators and given commit-access to the project. These
31 for commit-access log an issue or contact a WG member directly and it
34 Modifications of the contents of the readable-stream repository are
37 modification via pull request and it will be considered by the project
38 Collaborators. All pull requests must be reviewed and accepted by a
40 responsibility for the change. In the case of pull requests proposed
42 for sign-off. Consensus should be sought if additional Collaborators
[all …]
|
12345678910>>...14