# Triggering Renovate Reconfiguration

**URL:** <https://forum.codefloe.com/t/triggering-renovate-reconfiguration/89>\
**Category:** CI/CD\
**Created:** [March 25, 2026, 7:01am UTC](https://forum.codefloe.com/t/triggering-renovate-reconfiguration/89 "2026-03-25T07:01:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![johnhamelink](https://forum.codefloe.com/user_avatar/forum.codefloe.com/johnhamelink/32/140_2.png) [@johnhamelink](https://forum.codefloe.com/u/johnhamelink)\
**Post date:** [March 25, 2026, 7:01am UTC](https://forum.codefloe.com/t/triggering-renovate-reconfiguration/89/1 "2026-03-25T07:01:30Z")

</div>

Hi there,

I’m trying to setup Renovate for Nix on [crowci/crowci-flake](https://codefloe.com/crowci/crowci-flake). According to the [Renovate docs](https://docs.renovatebot.com/getting-started/installing-onboarding/#repository-re-configuration), I should be able to [create a PR](https://codefloe.com/crowci/crowci-flake/pulls/75) from a branch called `renovate/reconfigure`, and this should trigger a comment from renovate on the viability of the change? According to [Renovate | CodeFloe](https://docs.codefloe.com/usage/renovate/) the bot should run once an hour at 30 minutes past the hour. However even though I received the initial PR from renovate to setup the repo, I don’t seem to be getting subsequent updates from it. Is this because the repo was transferred from my user (johnhamelink) to the crowci org?

Thanks, JH

---

<div class="post-metadata">

**Author:** ![codefloe](https://forum.codefloe.com/user_avatar/forum.codefloe.com/codefloe/32/42_2.png) [@codefloe](https://forum.codefloe.com/u/codefloe)\
**Post date:** [March 25, 2026, 3:37pm UTC](https://forum.codefloe.com/t/triggering-renovate-reconfiguration/89/2 "2026-03-25T15:37:05Z")

</div>

> the bot should run once an hour at 30 minutes past the hour

Right! However it didn’t for a few days after we integrated the upstream changes from the operator we’re running. This brought back a filter on the repo topic `renovate` and therefore excluded most repos.

Discovery is now restored and your repo has been processed again!

We’ll also post a bit more information about the updated setup soon so everyone’s is informed!

---

<div class="post-metadata">

**Author:** ![johnhamelink](https://forum.codefloe.com/user_avatar/forum.codefloe.com/johnhamelink/32/140_2.png) [@johnhamelink](https://forum.codefloe.com/u/johnhamelink)\
**Post date:** [March 25, 2026, 4:01pm UTC](https://forum.codefloe.com/t/triggering-renovate-reconfiguration/89/3 "2026-03-25T16:01:18Z")

</div>

Thank you! As a new user to renovate I wasn’t sure if the issue was between the keyboard and the chair 😃 Appreciate it 🙂

---

<div class="post-metadata">

**Author:** ![johnhamelink](https://forum.codefloe.com/user_avatar/forum.codefloe.com/johnhamelink/32/140_2.png) [@johnhamelink](https://forum.codefloe.com/u/johnhamelink)\
**Post date:** [March 25, 2026, 7:52pm UTC](https://forum.codefloe.com/t/triggering-renovate-reconfiguration/89/4 "2026-03-25T19:52:18Z")

</div>

Hey there - one more (potential) issue. Renovate is now commenting on PRs, but after [merging](https://codefloe.com/crowci/crowci-flake/pulls/75), and checking the checkbox in the dependency dashboard to trigger an update, a [branch](https://codefloe.com/crowci/crowci-flake/commit/ce7cba496b5b80731d661e2c95fd84d7f88afbf8) was created, but no corresponding PR. Does this stem from a permissions issue perhaps?

Thanks again!

_ **EDIT** _: I merged that branch and then asked renovate to update again and this time I got a PR.

---

<div class="post-metadata">

**Author:** ![codefloe](https://forum.codefloe.com/user_avatar/forum.codefloe.com/codefloe/32/42_2.png) [@codefloe](https://forum.codefloe.com/u/codefloe)\
**Post date:** [March 26, 2026, 3:31pm UTC](https://forum.codefloe.com/t/triggering-renovate-reconfiguration/89/5 "2026-03-26T15:31:18Z")

</div>

There’s nothing influenced from our side what and how renovate does in detail _when_ it runs. We’re only responsibly for the schedule of the runs and the webhook behaviour (more info about that soon).
