search

RIOT-OS / riot-os.org

Sources of the RIOT website https://riot-os.org/.
4 stars 16 forks source link

github/workflows: add keepalive dummy commit step #103

Closed leandrolanzieri closed 1 year ago

leandrolanzieri commented 1 year ago

Github disables workflows from repos that have no activity in the last 60 days. This causes our deployment workflow to be disabled. To avoid hitting this limit, we can use the Keepalive Workflow action to add a commit every 50 days. This PR adds the action as a step of deployment, which runs everyday.

leandrolanzieri commented 1 year ago

For a first test we could change the days to 1 and see if this change works, and then go back to the default...

github-actions[bot] commented 1 year ago

🚀 PR preview deployed to https://RIOT-OS-riot-os-org-preview-103.surge.sh

miri64 commented 1 year ago

For a first test we could change the days to 1 and see if this change works, and then go back to the default...

yes please do that

Other than that, I would ACK this. The reasoning makes sense, as apparently just having a daily trigger is not enough (see https://github.com/marketplace/actions/keepalive-workflow#why)

leandrolanzieri commented 1 year ago

There, the limit is temporary set to 1 day

leandrolanzieri commented 1 year ago

The workflow is failing. It seems that for this to work we need to disable the branch protection in master...

miri64 commented 1 year ago

It seems that for this to work we need to disable the branch protection in master...

Mh, is there another solution maybe?

leandrolanzieri commented 1 year ago

It seems that for this to work we need to disable the branch protection in master...

Mh, is there another solution maybe?

Do you think this would work for this case? https://github.com/benjefferies/branch-protection-bot

leandrolanzieri commented 1 year ago

Here some more detailed guide https://www.turfemon.com/bump-version-protected-branch-github-actions

leandrolanzieri commented 1 year ago

Branch protection for workflows seems to be an open issue for GH... https://github.com/community/community/discussions/13836

miri64 commented 1 year ago

It seems that for this to work we need to disable the branch protection in master...

Mh, is there another solution maybe?

Do you think this would work for this case? https://github.com/benjefferies/branch-protection-bot

As far as I can see, the "include administrators" option does not exist in the recent config, instead there is a new "Do not allow bypassing the above settings" option now, that works similarly, but might not work with that bot (custom roles require Github Enterprise).

grafik

leandrolanzieri commented 10 months ago

Removed in https://github.com/RIOT-OS/riot-os.org/pull/113