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

7   * [Request Support](#request-support)
8   * [Report an Error or Bug](#report-an-error-or-bug)
9   * [Request a Feature](#request-a-feature)
11   * [Project Setup](#project-setup)
12   * [Contribute Documentation](#contribute-documentation)
13   * [Contribute Code](#contribute-code)
15   * [Provide Support on Issues](#provide-support-on-issues)
16   * [Label Issues](#label-issues)
17   * [Clean Up Issues and PRs](#clean-up-issues-and-prs)
18   * [Review Pull Requests](#review-pull-requests)
19   * [Merge Pull Requests](#merge-pull-requests)
20   * [Tag a Release](#tag-a-release)
21   * [Join the Project Team](#join-the-project-team)
30 The [Project Team](#join-the-project-team) looks forward to your contributions. ����✨
42 * The project team will [label the issue](#label-issues).
44 …'t respond to an issue for 30 days, the [issue will be closed](#clean-up-issues-and-prs). If you w…
56 * The project team will [label the issue](#label-issues).
57 …eam will ask you for those steps and mark the issue as `needs-repro`. Bugs with the `needs-repro` …
58 …rked `needs-fix`, as well as possibly other tags (such as `critical`), and the issue will be left …
59 …'t respond to an issue for 30 days, the [issue will be closed](#clean-up-issues-and-prs). If you w…
72 * The project team will [label the issue](#label-issues).
74 …eature-accepted`, which can then be done by either by a core team member or by anyone in the commu…
80 So you wanna contribute some code! That's great! This project uses GitHub Pull Requests to manage c…
82 …ub.com/articles/editing-files-in-another-user-s-repository/) without having to do any of this setu…
86 * [Install Rust](https://www.rust-lang.org/learn/get-started)
91 * `cargo test --features fancy`
95 **Note:** If you don't include the "fancy" feature, one of the doc-tests will fail.
99 …e tell others everything they need in order to be able to use this project -- or contribute to it.…
105 * [Set up the project](#project-setup).
108 * Re-read what you wrote, and run a spellchecker on it to make sure you didn't miss anything.
109 …mit message(s) using [conventional-changelog format](https://github.com/conventional-changelog/con…
110 * Go to https://github.com/zkat/miette/pulls and open a new pull request with your changes.
118 …ibution will be distributed to the masses next time the maintainers [tag a release](#tag-a-release)
130 * [Set up the project](#project-setup).
132 * Include any [additional documentation](#contribute-documentation) the changes might need.
134 …mit message(s) using [conventional-changelog format](https://github.com/conventional-changelog/con…
135 …fix>(deps): PKG@VERSION`, where `<prefix>` is any of the usual `conventional-changelog` prefixes, …
136 * Go to https://github.com/zkat/miette/pulls and open a new pull request with your changes.
143 …r changes, push, and ask for another review. Additional tags (such as `needs-tests`) will be added…
145 …ibution will be distributed to the masses next time the maintainers [tag a release](#tag-a-release)
149 [Needs Collaborator](#join-the-project-team): none
151 …not uncommon for most of the issues on an open source projects being support-related questions by …
153 … things that turn out to actually be other things, like bugs or feature requests. In that case, su…
166 * Be kind and patient with users -- often, folks who have run into confusing things might be upset …
170 [Needs Collaborator](#join-the-project-team): Issue Tracker
177 --- | --- | ---
180 `documentation` | Added to issues or pull requests that affect any of the documentation for the pro…
182 `enhancement` | Added to [feature requests](#request-a-feature), PRs, or documentation issues that …
183 …-the-project-team) to issues and PRs that they would like to get outside help for. Generally, this…
184 `in-progress` | Applied by [Committers](#join-the-project-team) to PRs that are pending some work b…
187 `starter` | Applied by [Committers](#join-the-project-team) to issues that they consider good intro…
189 … requests or adds primarily tests to the project. | If a PR is pending tests, that will be handled…
190 … entirely outside of its scope/sphere of influence. [Committers](#join-the-project-team) may apply…
194 [Needs Collaborator](#join-the-project-team): Issue Tracker
202 * Search the issue tracker for issues or PRs, and add the term `updated:<=YYYY-MM-DD`, where the da…
209 … See https://github.com/zkat/miette/blob/latest/CONTRIBUTING.md#clean-up-issues-and-prs for more d…
211 ## Review Pull Requests
213 [Needs Collaborator](#join-the-project-team): Issue Tracker
217 PR reviews use [GitHub's own review feature](https://help.github.com/articles/about-pull-request-re…
222 * *ALL PULL REQUESTS* should be covered by a test: either by a previously-failing test, an existing…
223 …ember who you think is better suited for the review, but still provide a non-approving review of y…
224 … time and care into what they've done (even if that's not obvious to you!) -- always respond with …
226 ## Merge Pull Requests
228 [Needs Collaborator](#join-the-project-team): Committer
230 TBD - need to hash out a bit more of this process.
234 [Needs Collaborator](#join-the-project-team): Committer
236 TBD - need to hash out a bit more of this process. The most important bit here is probably that all…
249 --- | ---
250 …-issues), [cleaning up old ones](#clean-up-issues-and-prs), and [reviewing pull requests](#review-…
251 Committer | Granted to contributors who want to handle the actual pull request merges, tagging new …