Skip to content

Use renovate-config repo directly for Renovate presets#220

Open
ErisDS wants to merge 1 commit into
mainfrom
chore/use-renovate-config-directly
Open

Use renovate-config repo directly for Renovate presets#220
ErisDS wants to merge 1 commit into
mainfrom
chore/use-renovate-config-directly

Conversation

@ErisDS
Copy link
Copy Markdown
Member

@ErisDS ErisDS commented Feb 25, 2026

Summary

  • replace package-style @tryghost: preset usage with github>TryGhost/renovate-config
  • standardize shared Renovate configuration on the dedicated renovate-config repository
  • remove indirection from older preset reference patterns

For a while, Renovate recommended using the .github repo to store shared presets. In our case, that setup is mostly just an alias to renovate-config, and it adds indirection and confusion about what our standard source should be.

Going forward, we don't want to use the .github repo for this. Having a dedicated renovate-config repo is more intuitive, so this switches to the direct preset source and standardizes where shared Renovate config comes from.
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Feb 25, 2026

Walkthrough

The Renovate configuration in package.json has been updated to change the extend target from "@TryGhost:quietJS" to "github>TryGhost/renovate-config". This is a single-line configuration modification with no functional code changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately summarizes the main change: updating the Renovate configuration to reference the renovate-config repository directly instead of the package-style preset.
Description check ✅ Passed The description is directly related to the changeset, providing clear context about replacing the preset reference pattern with the dedicated renovate-config repository.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/use-renovate-config-directly

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@package.json`:
- Line 47: The Renovate preset reference in package.json changed from the
npm-style "@tryghost:quietJS" to "github>TryGhost/renovate-config", which loads
the repo default (quiet.json5) not the named quietJS preset; either update the
dependency preset string to the explicit named form
"github>TryGhost/renovate-config:quietJS" if you want to preserve the original
quietJS behavior, or review/compare the settings in quiet.json5 vs quietJS to
confirm they produce identical Renovate behavior and adjust package.json
accordingly (look for the preset entry value "github>TryGhost/renovate-config"
and the old "@tryghost:quietJS" reference).

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9433981 and 3c8639a.

📒 Files selected for processing (1)
  • package.json

Comment thread package.json
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant