Enable long-lived sandboxes
Open
Nobody has claimed this yet.
sandboxes and sync
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Sandboxes are currently destroyed after merge, which prevents users having long-running sandboxes
What we need to do:
- Either: a) a sandbox has an option called "long lived", which means it is never destroyed on merge; or b) when merging a sandbox, there's a checkbox which says "destroy after merge"
- I think that's it?
Benefits:
- Set up a github sync to a sandbox
- use webhooks to call into sandboxes for live QA workflows
- don't have to keep recreating credentials and envs when constantly recreating new sandboxes (not sure how much of an issue this really is)
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the sandbox merge flow and where sandbox destruction is triggered. Resolve whether the behavior should be a long-lived sandbox option or a destroy-after-merge checkbox, then define the lifecycle and interface changes; the work is done when a merged sandbox can be retained or destroyed according to that choice.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100