Searched refs:PRs (Results 1 – 25 of 56) sorted by relevance
123
62 - Create **small PRs** that are narrowly focused on **addressing a single63 concern**. We often times receive PRs that are trying to fix several things65 both author's & review's time is wasted. Create more PRs to address different76 to address an issue. PRs with irrelevant changes won't be merged. If you do96 PRs with messy commit history are difficult to review and won't be merged.128 In addition to submitting PRs, a Contributor with Commit Access can:129 * Review PRs and merge once other checks and criteria pass.130 * Triage bugs and PRs and assign appropriate labels and reviewers.
57 - Create **small PRs** that are narrowly focused on **addressing a single58 concern**. We often times receive PRs that are trying to fix several things60 both author's & review's time is wasted. Create more PRs to address different71 to address an issue. PRs with irrelevant changes won't be merged. If you do87 PRs with messy commit history are difficult to review and won't be merged.
67 …PRs** that are narrowly focused on **addressing a single concern**. We often times receive PRs tha…73 … formatting unless you are already changing that line to address an issue. PRs with irrelevant cha…
58 * Create small PRs that are narrowly focused on addressing a single concern.59 We often receive PRs that are trying to fix several things at a time, but if61 & review's time is wasted. Create more PRs to address different concerns and69 line to address an issue. PRs with irrelevant changes won't be merged. If75 * Maintain clean commit history and use meaningful commit messages. PRs with
2 # code with old PRs.
47 For Cortex-A57 and Cortex-A72 CPUs, the Pull Requests (PRs) in this advisory51 For Cortex-A73 and Cortex-A75 CPUs, the PRs in this advisory invalidate the60 on the PRs in this advisory being deployed in order for those workarounds to89 | ``PSCI_VERSION`` baseline (without PRs in this advisory) | 515 |91 | ``PSCI_VERSION`` baseline (with PRs in this advisory) | 527 |
82 * Create **small PRs** that are narrowly focused on **addressing a single83 concern**. We often receive PRs that are trying to fix several things at a85 both author's & review's time is wasted. Create more PRs to address98 `git clang-format`. PRs with irrelevant changes won't be merged. If107 PRs with messy commit history are difficult to review and won't be merged.
43 PRs of additional well-established cases welcome.47 would prefer **not** to receive PRs to make this behavior more configurable.
74 Pull requests(PRs) are the primary mechanism we use to change Uuid. GitHub itself81 patches), we require PRs to relevant issues.83 Please open PRs against branch:129 * Find the [crates depending on `uuid`][dependent] and sending PRs to them,
3 <!-- Include relevant issues or PRs here, describe what changed and why -->
26 ## Submitting PRs28 We love PRs. Submit PRs [here](https://github.com/Kotlin/kotlinx.coroutines/pulls).34 * Base PRs against the `develop` branch.
17 !1 = !DIFile(filename: "b.cpp", directory: "/home/test/PRs/PR38990")
5 * [saethlin](https://github.com/saethlin) contributed many PRs (
167 populateRecords(ProfileRecordArray &PRs, ProfileRecord::PathAllocator &PA, in populateRecords() argument180 auto Record = PRs.AppendEmplace(PathArray{PA}, Node); in populateRecords()
48 !1 = !DIFile(filename: "a.cpp", directory: "/home/test/PRs/PR38990")
28 implementation of `GetMatchingPaths` but are not verified by the PRs introducing
31 ## Requirements for merged PRs33 For all PRs these steps are required before the PR is merged:
95 ## bors, the bot who merges all the PRs
391 ContextManager on all versions. Original PRs by Jelle Zijlstra and Ivan561 WrapperDescriptorType, minor bug-fixes. Original PRs by Jim818 ABC caching, etc. Original PRs by Jelle Zijlstra, Ivan Levkivskyi, Manuel
135 and `PRs <https://github.com/etingof/pyasn1/pulls>`_ at GitHub.
8 …nges are made to volk source files locally within ANGLE, please also make corresponding PRs so that