Searched +full:create +full:- +full:pull +full:- +full:request (Results 1 – 25 of 801) sorted by relevance
12345678910>>...33
| /external/yapf/.github/workflows/ |
| D | pre-commit-autoupdate.yml | 4 name: Keep pre-commit hooks up to date
8 - cron: '0 16 * * 5' # Every Friday 4pm
15 pull-requests: write
19 name: Detect outdated pre-commit hooks
20 runs-on: ubuntu-22.04
22 - uses: actions/checkout@eef61447b9ff4aafe5dcd4e0bbf5d482be7e7871 # v4.2.1
24 - name: Set up Python 3.11
25 uses: actions/setup-python@82c7e631bb3cdc910f68e0081d67478d79c6982d # v5.1.0
27 python-version: 3.11
29 - name: Install pre-commit
[all …]
|
| /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#)
29 1. Create your
30 [own fork](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-f…
[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/javaparser/ |
| D | CONTRIBUTING.md | 4 - There is some interesting information on the [wiki](https://github.com/javaparser/javaparser/wiki…
5 - We work on JavaParser because we like to, not because it earns us money. Please remember that we …
6 - Be sure to check [the coding guidelines](https://github.com/javaparser/javaparser/wiki/Coding-Gui…
7 - If you're new and like to casually contribute something, check out the [easy issues](https://gith…
8 - If you're new and would like to become a member, start your own project that uses JavaParser.
11 - If you start working on an issue, please say so with a comment in the issue.
12 - If you know how to fix a problem, please fix it and open a pull request instead of opening an iss…
18 …Pull Request. If you are not familiar with the Pull Requests, we suggest you to checkout the [Gith…
21 …our forked project, **create a branch** related to the issue you are working on. This is important…
23 …rser) and it should have a message offering to **create a pull request**. If it doesn't you can [c…
[all …]
|
| /external/ot-br-posix/ |
| D | CONTRIBUTING.md | 5 - [1 Code of Conduct](#code-of-conduct)
6 - [2 Bugs](#bugs)
7 - [3 New Features](#new-features)
8 - [4 Contributing Code](#contributing-code)
9 - [4.1 Initial Setup](#initial-setup)
10 - [4.2 Contributor License Agreement (CLA)](#contributor-license-agreement--cla-)
11 - [4.3 Submitting a Pull Request](#submitting-a-pull-request)
12 - [5 Contributing Documentation](#contributing-documentation)
20 …-br-posix/issues/new). The best bug reports provide a detailed description of the issue and step-b…
24 You can request a new feature by [submitting a GitHub Issue](https://github.com/openthread/ot-br-po…
[all …]
|
| /external/openthread/ |
| D | CONTRIBUTING.md | 5 - [1 Code of Conduct](#code-of-conduct)
6 - [2 Bugs](#bugs)
7 - [3 New Features](#new-features)
8 - [4 Contributing Code](#contributing-code)
9 - [4.1 Initial Setup](#initial-setup)
10 - [4.2 Contributor License Agreement (CLA)](#contributor-license-agreement--cla-)
11 - [4.3 Submitting a Pull Request](#submitting-a-pull-request)
12 - [5 Contributing Documentation](#contributing-documentation)
20 …e and step-by-step instructions for predictably reproducing the issue. Even better, you can [submi…
24 You can request a new feature by [submitting a GitHub Issue](https://github.com/openthread/openthre…
[all …]
|
| /external/python/six/ |
| D | CHANGES | 7 ------
9 - Pull request #388: Remove `URLopener` and `FancyURLopener` classes from
10 `urllib.request` when running on Python 3.14 or greater.
12 - Pull request #365, issue #283: `six.moves.UserDict` now points to
16 ------
18 - Pull request #343, issue #341, pull request #349: Port _SixMetaPathImporter to
22 ------
24 - Pull request #331: Optimize `six.ensure_str` and `six.ensure_binary`.
27 ------
29 - Issue #288, pull request #289: Add `six.assertNotRegex`.
[all …]
|
| /external/MPAndroidChart/ |
| D | CONTRIBUTING.md | 10 Bug-fixes and features often come from users of the MPAndroidChart library and improve it greatly. …
16 Search existing [issues] to see if your bug has already been reported or if a feature request alrea…
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 …** open [pull requests] AND existing [issues] to make sure what you want to do isn't already being…
24 1. **Create** a new branch based on `master`, and name it according to your changes
25 1. **Add** your commits, they MUST follow the [Commit Style](#commit-style) below
26 1. **Test** your changes by actually running the example app, or create a new example
27 1. **Create** a pull request, following the auto-generated template
33 …75](https://github.com/PhilJay/MPAndroidChart/pull/3975) for an example of a good-made-better pull…
[all …]
|
| /external/threetenbp/.github/workflows/ |
| D | tzdbupdate.yml | 6 - 'tzdb*'
8 - cron: '50 1 * * *'
16 contents: write # for peter-evans/create-pull-request to create branch
17 pull-requests: write # for peter-evans/create-pull-request to create a PR
18 runs-on: ubuntu-latest
21 - name: Checkout
26 - name: Set up JDK
27 uses: actions/setup-java@2c7a4878f5d120bd643426d54ae1209b29cc01a3 #v3.4.1
29 java-version: 8
33 - name: Maven version
[all …]
|
| /external/grpc-grpc/.github/workflows/ |
| D | pr-auto-fix.yaml | 7 actions: write # to cancel/stop running workflows (styfle/cancel-workflow-action)
8 contents: write # to create branch (peter-evans/create-pull-request)
9 pull-requests: write # to create a PR (peter-evans/create-pull-request)
11 runs-on: ubuntu-latest
14 - name: Get current time
15 uses: srfrnk/current-time@5a4163ad035ccd9a407ec9e519c3b6ba1b633d1e # v1.1.0
16 id: current-time
19 - name: Get current time
20 uses: srfrnk/current-time@5a4163ad035ccd9a407ec9e519c3b6ba1b633d1e # v1.1.0
21 id: current-time-with-day
[all …]
|
| /external/sdk-platform-java/test/integration/goldens/pubsub/src/com/google/cloud/pubsub/v1/ |
| D | SubscriptionAdminClient.java | 8 * https://www.apache.org/licenses/LICENSE-2.0
69 // AUTO-GENERATED DOCUMENTATION AND CLASS.
72 * consume messages from a subscription via the `Pull` method or by establishing a bi-directional
81 * // - It may require correct/in-range values for request initialization.
82 * // - It may require specifying regional endpoints when creating the service client as shown in
84 * try (SubscriptionAdminClient subscriptionAdminClient = SubscriptionAdminClient.create()) {
95 * such as threads. In the example above, try-with-resources is used, which automatically calls
102 * <li>A "flattened" method. With this type of method, the fields of the request type have been
105 * <li>A "request object" method. This type of method only takes one parameter, a request object,
106 * which must be constructed before the call. Not every API method will have a request object
[all …]
|
| /external/aws-sdk-java-v2/ |
| D | CONTRIBUTING.md | 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].
47 * If you are able to create one, include a [Minimal Working Example][mwe]
54 Feature requests are submitted through the [this][feature-request] page.
61 submit the feature request *before* working on any code changes. This will
[all …]
|
| /external/python/dateutil/ |
| D | CONTRIBUTING.md | 3 This document outlines the ways to contribute to `python-dateutil`. This is a fairly small, low-tra…
8 …ontribution - it's important to get feedback about how the library is failing, and there's no bett…
10 1. A minimal, reproducible example - a small, self-contained script that can reproduce the behavior…
13 - `dateutil`: `python -c 'import dateutil; print(dateutil.__version__)'`
14 - `Python`: `python --version`
16 3. A description of the problem - what *is* happening and what *should* happen.
18 While pull requests fixing bugs are accepted, they are *not* required - the bug report in itself is…
22 …res (ones where you don't have to put a lot of effort into the PR), a pull request is fine but sti…
24 ### Pull requests
26 …- improvements to documentation, bug fixes, feature implementations, fixes to the build system, e…
[all …]
|
| /external/google-cloud-java/.github/workflows/ |
| D | googleapis_hermetic_sync.yaml | 6 create-pull-request:
7 name: Create pull request for recent googleapis changes
8 runs-on: ubuntu-latest
10 - uses: actions/checkout@v3
12 repository: 'googleapis/google-cloud-java'
13 - name: Setup workspace
15 mkdir -p "${WORKSPACE}"
16 git config user.email "yoshi-code-bot[bot]@users.noreply.github.com"
17 git config user.name "yoshi-code-bot"
19 git clone --quiet --branch "${BASE_BRANCH}" --depth 1 \
[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…
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…
38 … Note: pull requests from forks will not run the automated tests without collaborator involvement …
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/iron-form/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
21 **If you are filing an issue to request a feature**, please provide a clear description of the feat…
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 …issue** or issues that will be closed by the pull request. Please refer to these issues in the pul…
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/iron-location/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
21 **If you are filing an issue to request a feature**, please provide a clear description of the feat…
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 …issue** or issues that will be closed by the pull request. Please refer to these issues in the pul…
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/iron-checked-element-behavior/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
21 **If you are filing an issue to request a feature**, please provide a clear description of the feat…
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 …issue** or issues that will be closed by the pull request. Please refer to these issues in the pul…
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/paper-menu/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
21 **If you are filing an issue to request a feature**, please provide a clear description of the feat…
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 …issue** or issues that will be closed by the pull request. Please refer to these issues in the pul…
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/font-roboto/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
21 **If you are filing an issue to request a feature**, please provide a clear description of the feat…
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 …issue** or issues that will be closed by the pull request. Please refer to these issues in the pul…
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/iron-meta/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
21 **If you are filing an issue to request a feature**, please provide a clear description of the feat…
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 …issue** or issues that will be closed by the pull request. Please refer to these issues in the pul…
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/paper-listbox/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
21 **If you are filing an issue to request a feature**, please provide a clear description of the feat…
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 …issue** or issues that will be closed by the pull request. Please refer to these issues in the pul…
[all …]
|
| /external/chromium-trace/catapult/third_party/polymer/components/paper-behaviors/ |
| D | CONTRIBUTING.md | 1 <!--
12 -->
21 **If you are filing an issue to request a feature**, please provide a clear description of the feat…
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 …issue** or issues that will be closed by the pull request. Please refer to these issues in the pul…
[all …]
|
12345678910>>...33