Help Operators to keep up with recipe updates #599
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: toolshed/organising#599
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It would be cool to have integration for a bot like renovate to get automatic pull request as a server operator for each recipe update. For renovate this would only help if the app env files are in a git repository. Maybe there are other update bots we can add integrations, that don't rely on a git forge
Nice, any how idea how this could be implemented? V curious...
So having a quick look at the renovate docs I think we need something like this:
Implement recipe versioning inside apps
Use the renovate regex manager to detect abra recipes
Add a datasource for the coopcloud recipes
Maybe also connect with renovate maintainers and see if we can get offical coopcloud integration in renovate
Sounds awesome to me! Any thoughts if it would be possible to also bump
coopcloud.versionlabel based onappimage bumps?Perhaps this could also pumped into a matrix channel for each recipe whereby Operators join that channel? There could be
Matrix Spacejust for Operators...