Skip to content

Lint against the release, and pull the shared files - #53

Merged
oblomov-dev merged 4 commits into
mainfrom
claude/repos-analysis-optimization-xejg9x
Aug 20, 2026
Merged

Lint against the release, and pull the shared files#53
oblomov-dev merged 4 commits into
mainfrom
claude/repos-analysis-optimization-xejg9x

Conversation

@oblomov-dev

Copy link
Copy Markdown
Member

What changes

Pin the framework to a release. Same unpinned git dependency as abap2UI5/samples: abaplint cloned the default branch, so this corpus was checked against the framework's development tip while its readers install a release. abaplint.jsonc now pins 1.143.0.

New check:pin (scripts/check-framework-pin.mjs, source in abap2UI5) holds the pin to one release and runs before any install; bump-framework-pin.yaml moves it weekly and lints at the new release before opening the pull request.

sync-shared.yaml pulls this repository's copies of the shared files from abap2UI5 and opens a PR when one moved.

The view-chain-layout skill is updated: it now describes what all four repositories actually do. This repository had already migrated to the linter's chain-house-layout rule and deleted its copy of chain-format.mjs — the skill still called that script "byte-identical in the two sample repositories" and did not mention this repo at all.

Plus @abap2ui5/render-runtime 0.1.1 → 0.2.2 (the 0.1 line was an artefact of the peer-range bug fixed in linter 0.2.2) and @abaplint/cli aligned on ^2.120.23.

How to test

  • npx abaplint abaplint.jsonc at the pin — 0 issues, 158 files.
  • node scripts/check-framework-pin.mjs — green, and negative-tested: a missing "branch" key and two configs naming different releases both fail.

Generated by Claude Code

claude added 4 commits August 20, 2026 06:53
Same pairing as abap2UI5/samples: render-runtime 0.1.1 sat next to linter
0.2.1 because the published peer range refused the matching pair, not
because 0.1 was wanted. Linter 0.2.2 widened the range, so both floors move
to ^0.2.2, and @abaplint/cli joins the ^2.120.23 the corpus declares.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fv6JYeoMYTAfwEaLupTgz5
Same unpinned git dependency as abap2UI5/samples: abaplint cloned the default
branch, so the corpus was checked against the framework's development tip
while its readers install a release. abaplint.jsonc now pins 1.143.0.

Verified: abaplint reports 0 issues over 158 files at the pin.

check:pin holds the pin to one release and runs before any install;
bump-framework-pin moves it weekly and lints at the new release before opening
the pull request.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fv6JYeoMYTAfwEaLupTgz5
The view-chain-layout skill now describes what all four repositories actually
do, and sync-shared is the workflow that will keep these copies current.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fv6JYeoMYTAfwEaLupTgz5
The workflow asked `github.event.repository.name` for the repository it is
running in, and its only triggers are `schedule` and `workflow_dispatch`. A
scheduled run carries no repository object, so the name would have come out
empty every Tuesday - the manifest call would have produced nothing and the
guard right below it would have failed the run. Loud rather than silent, which
is why the guard is there, but the feature would never have worked once.

GITHUB_REPOSITORY is always set. Verified by running the whole loop by hand
against abap2UI5/samples: five shared files resolved and copied, and the only
resulting diff is this workflow updating itself - which is the self-syncing
behaviour the shared-file entry describes.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Fv6JYeoMYTAfwEaLupTgz5
Copilot AI lite review requested due to automatic review settings August 20, 2026 09:30

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@oblomov-dev
oblomov-dev merged commit 00b5ec0 into main Aug 20, 2026
23 checks passed
@oblomov-dev
oblomov-dev deleted the claude/repos-analysis-optimization-xejg9x branch August 20, 2026 09:38
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.

3 participants