Lines Matching +full:stale +full:- +full:pr +full:- +full:label

4 organization's [governance rules](https://github.com/grpc/grpc-community/blob/master/governance.md)
5 and [contribution guidelines](https://github.com/grpc/grpc-community/blob/master/CONTRIBUTING.md) b…
8 howto](https://help.github.com/articles/about-pull-requests/)
10 …lease filter the issues list with the label ["disposition/help wanted"](https://github.com/grpc/gr…
11 …ts might have been closed in the past as a result of them being marked as stale due to there being…
22 … in [Building gRPC C++: Clone the repository](BUILDING.md#clone-the-repository-including-submodule…
32 - Prepare your development environment based on language-specific instructions in `src/YOUR-LANGUAG…
33 - The language-specific instructions might involve installing C/C++ prerequisites listed in
34 …[Building gRPC C++: Prerequisites](BUILDING.md#pre-requisites). This is because gRPC implementatio…
36 - Run
38   python tools/run_tests/run_tests.py -l YOUR_LANGUAGE --build_only
40 - To also run all the unit tests after building
42   python tools/run_tests/run_tests.py -l YOUR_LANGUAGE
45 You can also run `python tools/run_tests/run_tests.py --help` to discover useful command line flags…
50 To ease maintenance of language- and platform- specific build systems, many
62 - Create **small PRs** that are narrowly focused on **addressing a single
68 - For speculative changes, consider opening an issue and discussing it first.
72 - Provide a good **PR description** as a record of **what** change is being made
75 - Don't fix code style and formatting unless you are already changing that line
77   want to fix formatting or style, do that in a separate PR.
79 - If you are adding a new file, make sure it has the copyright message template
83 - Unless your PR is trivial, you should expect there will be reviewer comments
85   responsive to those comments, otherwise the PR will be closed after 2-3 weeks
88 - If you have non-trivial contributions, please consider adding an entry to [the
91   individual CLA, or your company, for corporate CLAs) in the same PR as your
95 - Maintain **clean commit history** and use **meaningful commit messages**.
97   Use `rebase -i upstream/master` to curate your commit history and/or to
101 - Keep your PR up to date with upstream/master (if there are merge conflicts,
104 - If you are regenerating the projects using
107   to generated and hand-written files make your PR difficult to review.
112 - **All tests need to be passing** before your change can be merged.
113   We recommend you **run tests locally** before creating your PR to catch
119 - Exceptions to the rules can be made if there's a compelling reason for doing