docs(contributing): add bootstrap troubleshooting guide#11442
Conversation
|
Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have the users @okwn on file. In order for us to review and merge your code, each contributor must visit https://cla.warp.dev to read and agree to our CLA. Once you have done so, please comment |
|
This PR is not linked to an issue that is marked with Issue-state enforcement details:
To continue, link this PR to a same-repo issue such as Powered by Oz |
github-actions
Bot
added
the
external-contributor
![oz-for-oss[bot]](https://avatars.githubusercontent.com/in/3450139?s=60&v=4){kind=small}
There was a problem hiding this comment.
This PR is not linked to an issue that is marked with ready-to-implement.
Issue-state enforcement details:
-
Associated same-repo issues checked: none
-
Required readiness label:
ready-to-implement
To continue, link this PR to a same-repo issue such as Closes #123 in the PR description, and make sure that issue has ready-to-implement.
Powered by Oz
Adds Bootstrap Troubleshooting with platform-specific guidance for macOS, Linux, Windows (WSL2), and network issues. Closes warpdotdev#11301
Closes warpdotdev#11301 (Windows bootstrap missing libclang and protoc; cargo build fails)
1 participant
Summary
Adds a Bootstrap Troubleshooting section to CONTRIBUTING.md with guidance for common failures:
Also adds a fallback guide for when bootstrap fails completely.
Why this matters
Bootstrap failures are a common blocker for new contributors. Clear, searchable troubleshooting steps in CONTRIBUTING.md reduce repeated GitHub issues and help contributors self-serve.
Changes
Validation
Read the CONTRIBUTING.md bootstrap section and verify the commands make sense for each platform.
Risk/Compatibility
Documentation only. No code changes.