Lines Matching +full:pull +full:- +full:requests

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
69 hear from you for 2 weeks or longer, we may close the pull request. You can
70 still send the pull request again once you have time to work on it.
72 Once a pull request is merged, we will take care of the rest and get it into
75 ## Pull Request Guidelines
87   support from a protobuf team member before sending us the pull request.
95   responsive to those comments, otherwise the PR will be closed after 2-3 weeks
99   -i upstream/main to curate your commit history and/or to bring in latest
112 * Apply the "release notes: yes" label if the pull request's description should
114   Apply the "release notes: no" label if the pull request's description should
118   pull request. This will make it easier to identify which languages the pull