[ORCA-282] Adds "Keep Alive" CI Step #27
Conversation
| @@ -52,7 +52,11 @@ jobs: | |||
| name: python-distribution-files | |||
| path: dist/ | |||
| retention-days: 1 | |||
|
|
|||
| # Prevent scheduled workflow from ever being paused | |||
There was a problem hiding this comment.
Interesting. Do we know what this action does to keep the workflow alive?
There was a problem hiding this comment.
It creates a dummy commit if the repo is >50 days stale when the scheduled job runs
There was a problem hiding this comment.
I'm updating it to do the dummy commit at 44 days instead. I realized that if 45-49 days had passed when a scheduled job ran it would not do the dummy commit before the 60-day limit.
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #27 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 28 28
Lines 874 874
Branches 138 99 -39
=========================================
Hits 874 874 ☔ View full report in Codecov by Sentry. |
|
Kudos, SonarCloud Quality Gate passed!
|
This PR introduces a CI step to prevent our scheduled workflow job from being paused due to the repository not being updated for >=60days. This step uses the Keep Alive Action. This Action will run each time our scheduled job does, and if it detects that this repo has not been updated for >=44 days it will push a dummy commit thus preventing our job from being paused after the 60-day limit is hit.