Hey. We are very excited about Trigger Dev and how it integrates into our development workflow, especially with branches, which work really well with GitHub and Supabase.
However, being unable to unarchive branches is becoming a growing concern.
It is very common for the team to work on several PRs simultaneously; some may stall and remain closed for a few days or weeks before being reworked.
While it's very easy to archive branches of merged PRs, we don't know for sure whether closed PRs are permanently closed, as they might be temporarily closed to free up resources.
We can buy more branches, but we cannot do this infinitely. Having a way to unarchive branches would be really helpful.
#Unarchiving branches
1 messages · Page 1 of 1 (latest)
Hi @fickle dew. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
Thank you for the kind words about Trigger.dev!
Regarding unarchiving preview branches: the knowledge sources do not contain any information about an unarchive feature. The documentation only covers:
- Archiving branches (via the CLI with
npx trigger.dev@latest preview archive, or from the dashboard) [Preview branches] - Creating new preview branches
There is no mention of an unarchive capability in the available documentation.
For your use case, the practical workarounds based on what the docs support are:
- Don't archive closed PRs immediately — only archive when you're confident the branch is truly done, rather than doing it automatically for all closed PRs.
- Re-deploy to a new/existing branch — when a stalled PR is reworked and reopened, you can redeploy to that preview branch using
npx trigger.dev@latest deploy --env preview --branch your-branch-name, which will create a fresh deployment for it. [Preview branches] - Purchase additional branch slots — on the Pro plan, extra branches are available at $10/month per branch. [Preview branch limits]
For the unarchive feature request specifically, I'd recommend reaching out to the Trigger.dev team directly via their Discord or email — this sounds like valuable product feedback they'd want to hear.
Note: you can ask me a follow up question by @ mentioning me again :speech_balloon:
@fickle dew Kapa.ai is still learning and improving, please let me know how I did by reacting below.
hey, thanks for the feedback, i have created a feature request for this which can be upvoted here: https://triggerdev.featurebase.app/p/unarchive-preview-branches
@fickle dew you can create the preview branch again with the same branch name and it will spin up a new one. You will lose the previous runs data if you do this though.
The archiving allows us to remove resources which is why we didn't add the unarchive feature… I don't think we can keep these around forever.
Archiving and unarchiving feels like a hack you want because the branches are too expensive for you?