Internal Config repository for multiple GitHub organizations #464
Unanswered
morremeyer
asked this question in
Q&A
Replies: 1 comment
-
I wonder if |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Description
We use multiple GitHub organizations with one GitHub App for renovate-ce that is owned by one of these orgs. In the same org, we also have a renovate-config repository that has our base config.
This repo is currently public, but we want to set it to internal.
However, once we do that, renovate-ce is not authenticated for that repository anymore once it runs for any repository outside of the org containing the renovate-config repository - which makes sense given that as far as I understand the App authentication, it is only valid for that one org while running for said org.
I discussed this with @rarkins a while ago and he suggested using a hostRule for that repo, which we implemented as
However, even with this hostRule, repositories outside of the org with the renovate-config repo still error.
Here's the full debug log for a run on of of the repositories in another org. I redacted the org names and repo ID of the repo renovate-ce ran for.
Log output
Beta Was this translation helpful? Give feedback.
All reactions