Replies: 1 comment
|
🕒 Discussion Activity Reminder 🕒 This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions: 1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as 2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own. 3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution. Note: This dormant notification will only apply to Discussions with the Thank you for helping bring this Discussion to a resolution! 💬 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Select Topic Area
Product Feedback
Body
GitHub Actions automatically disable workflows after 60 days of inactivity:
https://docs.github.com/en/actions/managing-workflow-runs/disabling-and-enabling-a-workflow
This is a reasonable resource/cost saving approach on GitHub's part. However, currently only new commits qualify as "activity". Apparently, creating release tags does not quality.
Here's a real use case of a PHP package serving as a wrapper for the corresponding PHP extension:
https://github.com/upscalesoftware/ext-swoole
https://github.com/upscalesoftware/ext-openswoole
The package is implemented in such a way that it references the Git tag as
self.version, so the same exact source code works for every version without having to modify & commit any files. The cron workflow checks for new versions and tags releases.I'd like to request to consider tag/release creation a valid activity besides commits to prevent workflows from being disabled.
All reactions