EST Branch to setup AI#2
Open
gqcorneby wants to merge 7 commits intorelease/0.9.7from
Open
Conversation
Tighten the naming convention from "kebab-case or camelCase" to camelCase-only for all custom/<feature> paths (backend and frontend). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds a new rule for schema-level upstream isolation (side tables vs column injection) that complements the existing custom-package-isolation file rule. Documents the openboxes-domain-model skill in CLAUDE.md. Ignores .claude/scheduled_tasks.lock runtime artifact.
Documents the load-bearing details for safely landing custom Liquibase
migrations on the EST fork:
- Placement: include line goes after the upstream release loop and
before the views rebuild so upstream migrations apply first, ours
second, and view rebuilds last.
- Aggregator clarification: adding includes inside custom/changelog.groovy
is never an upstream touch.
- FK ordering: include order in custom/changelog.groovy must put FK-target
files above FK-holder files; rollback runs in reverse-application order.
- Mandatory rollback {} block on every changeset.
- Liquibase id-collision protection via (id, author, filename) tuple —
use author 'eyeseetea' and the custom/ folder for namespace isolation.
Adds the one-time upstream-file touch to grails-app/migrations/changelog.groovy so every client and feature branch inherits the custom-migration entrypoint. New custom migrations now only need to: 1. Drop a file under grails-app/migrations/custom/<date>-<feature>.groovy 2. Append a one-line include to custom/changelog.groovy (which is ours) No more per-feature edits to the upstream master changelog. The aggregator ships empty — Liquibase loads the empty databaseChangeLog block as a no-op until real changesets are added. Updated .claude/rules/custom-package-isolation.md to reflect that the wiring is pre-installed; the rule no longer asks future authors to edit the upstream master changelog.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Setup ai config