github/puppeteer
0
0
Fork 0
mirror of https://github.com/puppeteer/puppeteer synced 2024-06-14 14:02:48 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: add bug triage guidelines (#9305)

Browse Source 
Co-authored-by: Mathias Bynens <mathias@qiwi.be>
This commit is contained in:
Alex Rudenko 2022-11-23 11:51:25 +01:00 committed by GitHub
parent bef1061c06
commit eda182741b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 21 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
docs/contributing.md
View File

@ -322,3 +322,21 @@ In the event release-please fails, the following needs to be done:
2. Create a GitHub release for each package, following the practice of previous 2. Create a GitHub release for each package, following the practice of previous
releases. releases.
## Bug triage guidelines
[Check incoming bug reports](https://github.com/puppeteer/puppeteer/issues) that do not have a `confirmed` or `needs-feedback` label:
1. Make sure the issue is labeled as either `bug` or `feature`.
2. If the issue does not have a clear repro or you cannot repro, ask for the repro and set the `needs-feedback` label.
3. Follow-up on the issues you previously asked for a feedback on (you should get a notification on GitHub when the user responds).
4. If the user does not provide feedback, the issue will be closed by the stale bot eventually.
5. If you are able to reproduce the issue, add the label `confirmed`.
6. If the bug is on the Chromium side, create a corresponding crbug.com issue, label the GitHub issue with the `upstream` label, and post a link to crbug.com in the comments.
7. If the issue is not related to either Puppeteer or Chromium, close the issue.
8. If the issue is about missing/incorrect documentation, label it as `documentation`.
Issues with PDFs:
1. If the issue reproduces using the regular print dialog and/or headful, [file a crbug.com against the `Blink>Layout` component](https://bugs.chromium.org/p/chromium/issues/entry?components=Blink%3ELayout).
2. If the issue is specific to Headless mode, [file an issue on crbug.com against the `Internals>Headless` component](https://bugs.chromium.org/p/chromium/issues/entry?components=Internals%3EHeadless).

7
docs/index.md
View File

@ -73,7 +73,7 @@ module.exports = {
After adding the configuration file, you will need to remove and reinstall After adding the configuration file, you will need to remove and reinstall
`puppeteer` for it to take effect. `puppeteer` for it to take effect.
See [Configuring Puppeteer](https://pptr.dev/guides/configuration) for more See the [configuration guide](https://pptr.dev/guides/configuration) for more
information. information.
#### `puppeteer-core` #### `puppeteer-core`
@ -209,12 +209,11 @@ run**.
#### Using Docker #### Using Docker
See our [guide on using Docker](https://pptr.dev/guides/docker). See our [Docker guide](https://pptr.dev/guides/docker).
#### Using Chrome Extensions #### Using Chrome Extensions
See our See our [Chrome extensions guide](https://pptr.dev/guides/chrome-extensions).
[guide on using Chrome extensions](https://pptr.dev/guides/chrome-extensions).
## Resources ## Resources