build_xdrip.yml: Disable keepalive action#626
build_xdrip.yml: Disable keepalive action#626JohanDegraeve merged 1 commit intoJohanDegraeve:developfrom
Conversation
The gautamkrishnar/keepalive-workflow has been taken down by GitHub, and GitHub Actions builds are failing due to this. Disabling the keepalive-workflow because the repo is no longer available. A permanent fix will need to be implemented later, this is a bandaid to prevent all build workflows to fail. This is also the same change that was made for LoopWorkspace: LoopKit/LoopWorkspace#248
|
Looks good to me as a temporary fix until the whole fastlane issue is fixed. |
Just a side note. We don't know if this is something that will be fixed. We know for certain, that the keepalive action is shutdown for good, see here or here (via maintainer), but not yet how or if this will be replaced. We could create a scheduled action that just pushes a dummy commit to a specific branch every x days… or instead of following the current (imho) problematic set-and-forget approach for browser build, require users to perform a single actions in their forks once every 2 months. |
|
Further side note: despite this just being a browser build / github workflow issue, this should probably be released as xDrip4iOS |
4 participants
The gautamkrishnar/keepalive-workflow has been taken down by GitHub, and GitHub Actions builds are failing due to this.
Disabling the keepalive-workflow because the repo is no longer available. A permanent fix will need to be implemented later, this is a bandaid to prevent all build workflows to fail.
Successful test of the workflow (the run was terminated manually after the critical steps had completed):
https://github.com/bjornoleh/xdripswift/actions/runs/14604108694
This is also the same change that was made for LoopWorkspace: LoopKit/LoopWorkspace#248, and a similar PR is being reviewed for Trio.