Feature Request
It would be very useful to see what PRs each Renovate run created, updated, or closed — both as a count summary and as a list of PR links.
Currently the UI shows per-project run status (completed/failed) but no information about what the run actually did. To check if Renovate created or updated PRs, you have to dig into executor pod logs.
What Renovate Already Logs
Renovate emits rich PR activity in its JSON logs that the operator could parse:
New PR created:
{"level":30, "msg":"Creating PR", "branch":"renovate/some-dep", "title":"Update X to Y", ...}Existing PR updated or unchanged:
{"level":20, "msg":"Pull Request #101 does not need updating", "branch":"renovate/rook-packages", ...}Git push with PR link:
{"level":20, "msg":"git push", "branch":"renovate/rook-packages", "result":{"remoteMessages":{"all":["Visit the existing pull request:","https://git.wxs.ro/k8s/flux/pulls/101 merges into main"]}}, ...}Suggested Implementation
Extend the existing log parser (logParser.go) to also extract PR activity:
- Count PRs created/updated/unchanged per run — parse "Creating PR", "Updating PR", "does not need updating" messages
- Store PR summary on the project status — e.g.
PRsCreated: 2, PRsUpdated: 1, PRsUnchanged: 3
- Show in UI — a small badge or column showing PR counts per project run, with optional expansion to show PR titles/links
This would make the operator UI much more useful for day-to-day monitoring — at a glance you could see which repos had actual dependency updates vs. just a clean scan.
Relationship to #35
This is complementary to the metrics work in #35. Metrics give Prometheus counters for alerting, while this feature provides human-readable PR details in the UI.
Feature Request
It would be very useful to see what PRs each Renovate run created, updated, or closed — both as a count summary and as a list of PR links.
Currently the UI shows per-project run status (completed/failed) but no information about what the run actually did. To check if Renovate created or updated PRs, you have to dig into executor pod logs.
What Renovate Already Logs
Renovate emits rich PR activity in its JSON logs that the operator could parse:
New PR created:
{"level":30, "msg":"Creating PR", "branch":"renovate/some-dep", "title":"Update X to Y", ...}Existing PR updated or unchanged:
{"level":20, "msg":"Pull Request #101 does not need updating", "branch":"renovate/rook-packages", ...}Git push with PR link:
{"level":20, "msg":"git push", "branch":"renovate/rook-packages", "result":{"remoteMessages":{"all":["Visit the existing pull request:","https://git.wxs.ro/k8s/flux/pulls/101 merges into main"]}}, ...}Suggested Implementation
Extend the existing log parser (
logParser.go) to also extract PR activity:PRsCreated: 2, PRsUpdated: 1, PRsUnchanged: 3This would make the operator UI much more useful for day-to-day monitoring — at a glance you could see which repos had actual dependency updates vs. just a clean scan.
Relationship to #35
This is complementary to the metrics work in #35. Metrics give Prometheus counters for alerting, while this feature provides human-readable PR details in the UI.