ci: generated files on Renovate's branches come from the regenerate bot (bots/regenerate) #27
No reviewers
Labels
No labels
ansible
bug
ci
dependencies
digest
docker
documentation
duplicate
enhancement
fix
go
good first issue
help wanted
invalid
javascript
major
minor
patch
php
python
question
released
security
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
dawid/taschenrechner!27
Loading…
Reference in a new issue
No description provided.
Delete branch "ci-regenerate-bot"
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?
The files this repository generates and commits are now regenerated on Renovate's branches by the regenerate bot, a workflow in
bots/regenerate(HomeLab #156). Before, the job useddawid/ci-actions/renovate-regenerate, with the bot's token in this repository's jobs. The bot now builds on the CI hosts without any token. A separate job with the token pushes only the bot's own commits, and only within the files each step may change..forgejo/workflows/regenerate.ymlis removed;test.yml's comment names the bot.REGENERATE_TOKENis deleted when HomeLab #156 is deployed.Merge before HomeLab #156 is deployed. That deployment deletes
renovate-regeneratefromci-actions, and a workflow still naming it would fail. Until then, Renovate's branches here get no regeneration. A Renovate branch made before this merge still carries the old step until Renovate rebases it.🤖 Generated with Claude Code
Tests of Test / test: passed
134 passed, 0 failed, 0 skipped (134 tests, 0.0 s) · coverage 57.9% (-0.0 against main)
Of
ac54a76f5c, the run, updated by every run.