Allow personal accounts to set a default GitHub Actions retention period across repositories #210681
Unanswered
ThePieMonster
asked this question in
Actions
Replies: 1 comment
|
💬 Your Product Feedback Has Been Submitted 🎉 Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users. Here's what you can expect moving forward ⏩
Where to look to see what's shipping 👀
What you can do in the meantime 💻
As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities. Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐ |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
🏷️ Discussion Type
Product Feedback
💬 Feature/Topic Area
Other
Discussion Details
Request
Please add a personal account setting for the default GitHub Actions retention period, including a one-day option, covering both existing and future personally owned repositories.
Problem and use case
Personal account owners may want short-lived CI artifacts to expire after one day across their repositories. Configuring this currently requires updating each repository separately or maintaining retention settings in individual artifact-upload steps.
Long retention periods can allow temporary artifacts to accumulate and exhaust storage quotas. Changing repository retention also leaves existing artifact expiration dates unchanged, requiring separate cleanup.
The repository API makes the initial configuration scriptable, but future repositories still require another update or ongoing automation. A personal account default would avoid this repeated maintenance.
Proposed behavior
The UI should explain that the shared setting also affects logs, workflow runs, checks, and commit statuses, and that changing it applies prospectively to new data.
Benefit
This would give individual developers a central way to control retention and storage usage without moving their repositories into an organization. Organizations already have a central retention setting; personal accounts would benefit from a comparable default.
References
All reactions