I tried setting up a gitea action for that but failed since the 'create pull request' api calls based on the github api and dont work for the gitea api.
the action.yml was deleted here, for orientation if its picked up again: 6a7a8a569c
Either we wait till that problem is fixed somewhere upstream or we run some script/cronjob to take care of that on some of our hosts
I tried setting up a gitea action for that but failed since the 'create pull request' api calls based on the github api and dont work for the gitea api.
the action.yml was deleted here, for orientation if its picked up again: 6a7a8a569c7b614a69000dc5cea125b6d7770c7a
The whole thing was based on https://github.com/Mic92/dotfiles/blob/main/.github/workflows/update-flake-lock.yml
Either we wait till that problem is fixed somewhere upstream or we run some script/cronjob to take care of that on some of our hosts
kalipso
changed title from Automatically update flake look at given period to Automatically update flake lock at given period2024-10-25 00:34:35 +02:00
ahtlon
added the Updates label 2024-10-29 17:40:52 +01:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I tried setting up a gitea action for that but failed since the 'create pull request' api calls based on the github api and dont work for the gitea api.
the action.yml was deleted here, for orientation if its picked up again:
6a7a8a569cThe whole thing was based on https://github.com/Mic92/dotfiles/blob/main/.github/workflows/update-flake-lock.yml
Either we wait till that problem is fixed somewhere upstream or we run some script/cronjob to take care of that on some of our hosts
Automatically update flake look at given periodto Automatically update flake lock at given periodDone with
6182318a29