rsnext/.github
Balázs Orbán aa35aa13f1
chore: clarify GitHub action (bot) comments (#34546)
For anyone landing on this PR, if you are new to contributing to open source, here is a helpful video with some good tips: [How to Contribute to Open Source (Next.js)
](https://www.youtube.com/watch?v=cuoNzXFLitc)

We use two GitHub Actions (here bots) to help us maintain the project better:

1. Stalebot

When an issue is triaged, we look for a reproduction and clear steps to reproduce the reported issue. This helps us identify bugs easier, which will result in a quicker resolution of the bug.

Skipping these steps could mean that we will not be able to investigate. In these cases, the issue will receive a `please add a complete reproduction` label, that indicates to the original poster (or those following along in the issue) that we would like them to post the missed steps. Unless that happens within 30 days, we are marking the issue as stale. A day after, the issue is automatically closed.

If someone finds this now-closed issue later, through the Stalebot we encourage that a new issue will be opened and reference the old one if it holds important/relevant contextual information. The reason is that newer releases might have already fixed the issue that was reported in the first place. This is indicated in the bug report issue template forms.

2. Lockbot

This bot is similar to Stalebot, but it strictly operates on **already closed/resolved** issues, it **never** closes ongoing/open issue discussions.

An issue can be closed for multiple reasons. It either has been closed by the original poster because they found the solution, or a PR merge included a fix in a recent Next.js release. It is important to look for the reason before commenting.

If the issue was seemingly locked by accident, through the Lockbot comment we encourage that a new issue will be opened and reference the old one if it holds important/relevant contextual information. The reason is that newer releases might have already fixed the issue that was reported in the first place. This is indicated in the bug report issue template forms.


Important: Issues can be closed/locked by accident, and we encourage everyone to feel welcome opening a new case and reference back to the old issue. Our team values everyone's opinion and we would like to make sure that we resolve any confusion in each individual case.
2022-02-18 16:42:05 +00:00
..
actions/next-stats-action Extract next-swc Rust code into its own package (#31635) 2021-11-21 12:59:56 +01:00
ISSUE_TEMPLATE Update 2.example_bug_report.yml 2022-02-16 21:49:54 +01:00
workflows chore: clarify GitHub action (bot) comments (#34546) 2022-02-18 16:42:05 +00:00
.kodiak.toml Maintain co-authors when kodiak merges (#31316) 2021-11-11 12:21:25 -06:00
CODEOWNERS Update codeowners (#32583) 2021-12-16 13:32:04 -06:00
labeler.json Updated Maedahs name in label gen config (#32005) 2021-12-01 10:20:11 -06:00
pull_request_template.md add linting instructions (#30123) 2021-10-20 21:52:23 -05:00