Skip to content

fix(renovate): inherit dryvist/.github master instead of a divergent fork#361

Merged
JacobPEvans-personal merged 1 commit into
mainfrom
chore/renovate-shim-to-dryvist
Jun 29, 2026
Merged

fix(renovate): inherit dryvist/.github master instead of a divergent fork#361
JacobPEvans-personal merged 1 commit into
mainfrom
chore/renovate-shim-to-dryvist

Conversation

@JacobPEvans-personal

Copy link
Copy Markdown
Owner

Problem

JacobPEvans-personal/.github carried its own standalone renovate-presets.json (9.5 KB) + renovate-grouping.json that extended only each other — they did not extend the dryvist/.github master. Every JacobPEvans-personal repo references local>JacobPEvans/.github:renovate-presets (the JacobPEvans login redirects here), so the entire personal-repo chain never reached the documented single source of truth:

"dryvist/.github is the MASTER source of truth for Renovate policy across ALL dryvist AND JacobPEvans repos. JacobPEvans/.github extends THIS, never the reverse."

The fork had drifted (9.5 KB vs the master's 12.7 KB).

Fix

Replace both files with thin shims that extend the dryvist master:

  • renovate-presets.jsonextends: ["local>dryvist/.github:renovate-presets"]
  • renovate-grouping.jsonextends: ["local>dryvist/.github:renovate-grouping"]

All ~14 personal repos keep their existing :renovate-presets references (no per-repo churn) and now boil up to the single dryvist master. The divergent local policy is dropped in favor of the master (a strict superset). Add future policy in dryvist/.github only.

Part of a workspace-wide sweep. Companion fixes: dryvist/nix-ai-server#16 and dryvist/homelab-schemas#15 (deleted stale shadowed renovate.json5 duplicates).

…fork

JacobPEvans-personal/.github carried its own standalone renovate-presets.json
(9.5KB) + renovate-grouping.json that did NOT extend the dryvist/.github master
— they extended only each other. Every JacobPEvans-personal repo references
`local>JacobPEvans/.github:renovate-presets` (redirects here), so the whole
personal-repo chain never reached the documented single source of truth
("dryvist/.github is the MASTER for Renovate policy across ALL dryvist AND
JacobPEvans repos; JacobPEvans/.github extends THIS").

Replace both files with thin shims that extend the dryvist master:
- renovate-presets.json  -> extends local>dryvist/.github:renovate-presets
- renovate-grouping.json -> extends local>dryvist/.github:renovate-grouping

Consumers keep their existing `:renovate-presets` references (no per-repo
churn); they now boil up to dryvist. The divergent local policy is dropped in
favor of the master (a strict superset). Add future policy in dryvist/.github
only, never here.

Assisted-by: Claude:claude-opus-4-8[1m]
Claude-Session: https://claude.ai/code/session_01CYau7MWswJikoctB9MUgcZ
Copilot AI review requested due to automatic review settings June 28, 2026 23:25

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

This PR removes the previously divergent Renovate policy/config in JacobPEvans-personal/.github and replaces it with thin “shim” presets that inherit the Renovate master policy from dryvist/.github, restoring a single source of truth across dryvist + JacobPEvans repositories.

Changes:

  • Replaced the local renovate-presets.json contents with an extends pass-through to local>dryvist/.github:renovate-presets.
  • Replaced the local renovate-grouping.json contents with an extends pass-through to local>dryvist/.github:renovate-grouping.
  • Updated descriptions to explicitly document the new inheritance model and discourage future local divergence.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
renovate-presets.json Converts the org preset into a thin shim that delegates Renovate policy to dryvist/.github.
renovate-grouping.json Converts grouping rules into a thin shim that delegates to dryvist/.github grouping.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request refactors the Renovate configuration for the JacobPEvans-personal organization to align with the dryvist/.github master repository. By transforming existing configuration files into thin shims that extend the master policy, the change establishes a single source of truth for dependency management across all associated repositories, preventing future configuration divergence.

Highlights

  • Consolidation of Renovate Policy: Replaced standalone Renovate configuration files with thin shims that inherit directly from the dryvist/.github master repository.
  • Single Source of Truth: Ensured that all JacobPEvans-personal repositories now follow the centralized Renovate policy defined in dryvist/.github, eliminating configuration drift.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.


Configs drifted far and wide, Now they have nowhere to hide. Inheriting from master source, Renovate stays on its course.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@JacobPEvans-personal JacobPEvans-personal merged commit 76090f9 into main Jun 29, 2026
3 checks passed
@JacobPEvans-personal JacobPEvans-personal deleted the chore/renovate-shim-to-dryvist branch June 29, 2026 00:17
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.

2 participants