Skip to content

chore(pr-lens): stop adding a block to PR descriptions - #106

Merged
AojdevStudio merged 2 commits into
mainfrom
chore/pr-lens-no-description
Oct 26, 2026
Merged

AojdevStudio merged 2 commits into
mainfrom
chore/pr-lens-no-description

Conversation

@AojdevStudio

Copy link
Copy Markdown
Owner

Problem

The PR Lens app appends a description block after the last line of every PR body. The pr-kit check needs that last line to be the Changes made by line. So the PR body contract check fails on every new PR, for example #101 and #105.

Change

A new .github/pr-lens.yml turns off the description block. PR Lens still posts its diagrams as a PR comment.

schemaVersion: 0.2.0
github:
  description: false

Proof

Check Before After
PR body contract on #105 fails: the last line is exactly "Changes made by <model> via <harness>" not proven until merge, see below
Config parses with the expected values no file {"schemaVersion":"0.2.0","github":{"description":false}}

PR Lens source, config.ts: github.description is a boolean, and false leaves descriptions alone. schemaVersion has no .optional(), so the parser rejects a file without it. The current version is 0.2.0.

Skipped check: PR Lens probably reads this file from the default branch. So the effect on new PRs shows only after merge.

Review

Finding Disposition Reason
No schemaVersion, so PR Lens rejects the whole file Fix bd0b90a adds schemaVersion: 0.2.0, checked against SCHEMA_VERSION in the PR Lens primitives.ts.
The setting stops only new blocks, not blocks already in PR bodies Fix The block was removed from the #105 body by hand. #101 gets the same cleanup.

Merge danger

Door: two-way. Revert this PR to undo it.
Blast radius: low. Only PR Lens reads this file, and the PR Lens comment and check do not depend on the description block.

Changes made by Claude Opus 5.5 via Claude Code

@coldtea-pr-lens

Copy link
Copy Markdown

Note

The title starts with chore(pr-lens):, so PR Lens left this pull request undrawn. Comment @pr-lens draw to draw it

github.comment.notice: false in .github/pr-lens.yml turns this note off

@coderabbitai

coderabbitai Bot commented Oct 26, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 52 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration
Commits

Reviewing files that changed from the base of the PR and between b2d6e41 and bd0b90a.

Files selected for processing: 1
  • .github/pr-lens.yml
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@pullfrog pullfrog Bot 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.

✅ No new issues found.

Reviewed changes in .github/pr-lens.yml against the upstream PR Lens configuration contract and the repository's PR-body checker.

  • Description updates disabled: github.description: false prevents PR Lens from appending content after the required attribution line while retaining default diagram comments and automatic drawing.
  • Required schema version supplied: schemaVersion: 0.2.0 matches the supported upstream contract. A local YAML assertion passed with the expected string and boolean types.

Hosted-app behavior was not exercised end to end. Upstream configuration documentation says GitHub settings are read from the PR's head commit, rather than only after merge.

Pullfrog  | View workflow run | Using gpt-6.1-sol | 𝕏

@AojdevStudio
AojdevStudio merged commit 4486087 into main Oct 26, 2026
8 checks passed
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