sandboxes: version pruning and squashing
Open
Nobody has claimed this yet.
needs detail
sandboxes and sync
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
Every time a project is merged or deleted (or both!), we need to prune the version histories of all workflows. This means removing everything older than the common version with main.
When squashing,we basically just remove the last history entry and add a new one (to update the timestamp)
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 code paths for project merge and deletion, then locate how workflow version histories are stored and updated. Done means histories are pruned to the common version with main and squashing removes the final entry before adding a replacement with an updated timestamp.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100