Initial public release of Warp.

Repo-Sync-Origin: warpdotdev/warp-internal@12af1d983b
This commit is contained in:
David Stern
2026-04-28 08:43:33 -05:00
commit 0dbd3d567a
4982 changed files with 1431549 additions and 0 deletions
@@ -0,0 +1,10 @@
## Justification
Why do we need this cherry-pick? Does it align with our [guidelines](https://www.notion.so/warpdev/How-We-Work-Releases-8e7d7cb4f2ca44b880fa1d0ae4876473?pvs=4)?
## Testing
How did you test this change? What automated tests did you add? If you didn't add any new tests, what's your justification for not adding any?
## Validation
- [ ] I've cut a new WarpDev to validate this change
- [ ] If this change is Wednesday or later, there's a dedicated bug bash scheduled for either this change or the release
@@ -0,0 +1,38 @@
This PR template helps ensure that as we launch new features we appropriately communicate, track, document, make them accessible, etc.
## PRD checklist
- [ ] Plan for how to measure success quantified by metrics
## Coding checklist
- [ ] Test in dev for a week
- [ ] Telemetry in code
- [ ] A11y (if applicable, see [testing a11y guide](https://docs.google.com/document/d/1-H0bWss5Qw18ZpIYg-RUvN7_db1MVdWfOb5UF_GLxNc/edit?usp=sharing) for more info)
- [ ] Add to Command Palette (if applicable)
- [ ] Add toggle setting(s) to command palette (if applicable)
- [ ] Add to Mac Menu (if applicable)
- [ ] Add keybinding (if applicable), see [actions audit for inspiration](https://docs.google.com/spreadsheets/d/1C56ZIqDGjJi873-HAPdnT2DofC3Z6G-aJMYeQeERHx4/edit#gid=0)
- [ ] Sanity check within the app that it does not clash other keybindings
- [ ] No sensitive info in logs
- [ ] No crashes on dev related to the feature
- [ ] No performance regression on dev. See [dashboard](https://warp.metabaseapp.com/dashboard/1519-dev-performance-by-version?shell=zsh)
- [ ] Feature works fine, and no regression, over SSH. See [instructions](https://github.com/warpdotdev/warp-internal/tree/master/app/tests/ssh/README.md) on how to get a VM.
- [ ] Have we explicitly brainstormed how this feature will be discovered by developers?
- [ ] Link to Figma mocks
- [ ] Tested on multiple themes (both dark and light)
- [ ] If the feature being released relies on some server API, has that server API been stable on production for at least one full server release cycle? See [here](https://www.notion.so/warpdev/How-to-add-a-new-full-stack-feature-8412cede405a4ec194b32bdd4b951035?pvs=4#73b202f939834b97ab1fbdf7fc82cd53) for more details.
## Content checklist
- [ ] Help content
- [ ] Changelog entry (add entry below)
- [ ] [Telemetry entry](https://docs.warp.dev/getting-started/privacy#exhaustive-telemetry-table) (if applicable)
- [ ] Metrics dashboard in Metabase
- [ ] Tweet (if appropriate)
- [ ] Blog post (if appropriate)
## Changelog
CHANGELOG-NEW-FEATURE: {{Insert a changelog entry here}}