Lines Matching +full:close +full:- +full:issue +full:- +full:message
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. ����✨
36 * Open an Issue at https://github.com/zkat/miette/issues
42 * The project team will [label the issue](#label-issues).
44 …issue for 30 days, the [issue will be closed](#clean-up-issues-and-prs). If you want to come back …
50 * Open an Issue at https://github.com/zkat/miette/issues
56 * The project team will [label the issue](#label-issues).
57 …issue with your provided steps. If there are no repro steps or no obvious way to reproduce the iss…
58 …issue, it will be marked `needs-fix`, as well as possibly other tags (such as `critical`), and the…
59 …issue for 30 days, the [issue will be closed](#clean-up-issues-and-prs). If you want to come back …
66 * Open an Issue at https://github.com/zkat/miette/issues
72 * The project team will [label the issue](#label-issues).
73 …questions to understand its purpose and any relevant requirements. If the issue is closed, the tea…
74 …eature-accepted`, which can then be done by either by a core team member or by anyone in the commu…
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 …message(s) using [conventional-changelog format](https://github.com/conventional-changelog/convent…
111 …s connected to an open issue, add a line in your PR's description that says `Fixes: #123`, where `…
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 …ar, concise commit message(s) using [conventional-changelog format](https://github.com/conventiona…
135 …ual commits, and the message must use the format: `<prefix>(deps): PKG@VERSION`, where `<prefix>` …
137 …s connected to an open issue, add a line in your PR's description that says `Fixes: #123`, where `…
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 …In that case, suss out the details with the person who filed the original issue, add a comment exp…
157 * Go to the issue tracker and [filter open issues by the `support` label](https://github.com/zkat/m…
159 * Respond to the issue with whatever details are needed to clarify the question, or get more detail…
160 …ps up and things are clarified, either close the issue, or ask the original issue filer (or a main…
166 …-- often, folks who have run into confusing things might be upset or impatient. This is ok. Try to…
170 [Needs Collaborator](#join-the-project-team): Issue Tracker
172 …y and accurately. All other tasks involving issues ultimately rely on the issue being classified i…
174 …issue labels according to the table below. If you're unsure about what label to apply, skip the is…
177 --- | --- | ---
181 …e issue as another one that's been previously labeled. | Duplicate issues should be marked and clo…
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…
185 `performance` | This issue or PR is directly related to improving performance. |
187 `starter` | Applied by [Committers](#join-the-project-team) to issues that they consider good intro…
188 `support` | This issue is either asking a question about how to use the project, clarifying the rea…
189 …issue or PR either requests or adds primarily tests to the project. | If a PR is pending tests, th…
190 …ters](#join-the-project-team) may apply this label and close an issue or PR if they decide to pass…
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…
203 * Go through each issue *from oldest to newest*, and close them if **all of the following are true*…
209 …message when closing saying "Cleaning up stale issue. Please reopen or ping us if and when you're …
213 [Needs Collaborator](#join-the-project-team): Issue Tracker
215 … on a PR, add feedback, etc, PRs are only *approved* by team members with Issue Tracker or higher …
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 …
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 Issue Tracker | Granted to contributors who express a strong interest in spending time on the proje…