Chrome DevTools for coding agents
docs: revise contribution process and add release process (#1134)
Alex Rudenkod7d26a103b84
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex f32e2385..12ee96ac 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -23,7 +23,7 @@ sign a new one.This project follows[Google's Open Source Community Guidelines](https://opensource.google/conduct/).-## Contribution process+## Development process### Code reviews@@ -53,6 +53,13 @@ completed:features (we want to avoid features that offer some tools but cannot be usedsuccessfully to debug things).+### Release process++Releasing `chrome-devtools-mcp` is automated by GitHub Actions. To release a new+version, [search for a PR titled `chore(main): release chrome-devtools-mcp`](https://github.com/ChromeDevTools/chrome-devtools-mcp/pulls?q=is%3Apr+is%3Aopen+%22chore%28main%29%3A+release+chrome-devtools-mcp%22)+and review, test, and land it. The release PR is automatically opened if there+are any changes on the main branch that show up in the changelog.+## InstallationCheck that you are using node version specified in .nvmrc, then run following commands: