Skip to content

Conversation

@MichaReiser
Copy link
Member

Summary

Automatically deploy the Red Knot playground for every commit to main (because we're moving fast ;)).

Test Plan

@MichaReiser MichaReiser force-pushed the micha/deploy-knot-playground branch from 531d655 to 613fe37 Compare March 18, 2025 16:32
@MichaReiser MichaReiser added ci Related to internal CI tooling ty Multi-file analysis & type inference labels Mar 18, 2025
@MichaReiser
Copy link
Member Author

I don't think I can test this without merging :(

@MichaReiser MichaReiser merged commit cc3ddaf into main Mar 18, 2025
22 checks passed
@MichaReiser MichaReiser deleted the micha/deploy-knot-playground branch March 18, 2025 16:40
dcreager added a commit that referenced this pull request Mar 18, 2025
* main:
  [playground] Avoid concurrent deployments (#16834)
  [red-knot] Infer `lambda` return type as `Unknown` (#16695)
  [red-knot] Move `name` field on parameter kind (#16830)
  [red-knot] Emit errors for more AST nodes that are invalid (or only valid in specific contexts) in type expressions (#16822)
  [playground] Use cursor for clickable elements (#16833)
  [red-knot] Deploy playground on main (#16832)
  Red Knot Playground (#12681)
  [syntax-errors] PEP 701 f-strings before Python 3.12 (#16543)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ci Related to internal CI tooling ty Multi-file analysis & type inference

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants