ability to control the maximum number of deployments stored
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 37.4k
- Forks
- 3k
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 73
Description
What problem will this feature address?
If in a day i along with colleagues push 10-15 times in total, that means only that days works deployments will be saved, it would be nice to control the number of deployments to keep instead of hard 10. Allows people to see further back deployments at their own choice.
Describe the solution you'd like
Having a setting in the Advanced tab of each node (different for each site but with default of 10)
Describe alternatives you've considered
Don't push as much or work on seperate branches but sometimes on a solo or duo project this is not effective
Additional context
No response
Will you send a PR to implement it?
Maybe, need help
Contributor guide
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
No files or tests are named. Start by locating the current hard-coded deployment retention limit and the Advanced settings entry point for each node; done means each site can configure its retained deployment count while defaulting to 10.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100