Skip to content

docs(contributing): stop asking UI changes for a screenshot - #826

Merged
devswha merged 1 commit into
mainfrom
docs/drop-screenshot-rule
Oct 11, 2026
Merged

devswha merged 1 commit into
mainfrom
docs/drop-screenshot-rule

Conversation

@devswha

@devswha devswha commented Oct 11, 2026

Copy link
Copy Markdown
Owner

Change

The pull request template and CONTRIBUTING.md asked every UI change to attach a screenshot or recording. The maintainer does not review from those images, and a PR opened from the command line cannot attach one, so recent PRs (#823, #824) carried a note saying the images were captured but not attached. Remove the requirement from both places.

Unchanged: the rules about where a capture comes from when someone does make one (AGENTS.md and CONTRIBUTING.md: a demo or test session, never a live one).

Validation

Documentation only. git diff touches one sentence in .github/pull_request_template.md and one in CONTRIBUTING.md; a search of .github, CONTRIBUTING.md, the AGENTS.md files and docs/development.md found no other place that asks for an attachment.

Release

No app or runtime change.

@coderabbitai

coderabbitai Bot commented Oct 11, 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 7 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 4 included reviews currently available.

Learn how review limits work.

Review configuration:

⚙️ Run configuration
  • Configuration used: Repository: devswha/herdr-web-ui/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 311e8d13-fa58-4d67-a008-8d4c86e96a67

📥 Commits

Reviewing files that changed from the base of the PR and between 6e6eaaf and 56b6fb4.


📒 Files selected for processing (2)
  • .github/pull_request_template.md
  • CONTRIBUTING.md

  • 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.

@devswha
devswha merged commit fc4a844 into main Oct 11, 2026
9 checks passed
@devswha
devswha deleted the docs/drop-screenshot-rule branch October 11, 2026 18:13
devswha added a commit that referenced this pull request Oct 11, 2026
## Change

Release 0.4.7, from main at 80ca9bb (47 PRs since v0.4.6).

- `package.json` and `herdr-plugin.toml`: 0.4.7.
- CHANGELOG: `[Unreleased]` becomes `[0.4.7] - 2026-10-12`, with the
compare links.
- #513's entry moves out of the 0.4.0 section, where its branch's merge
left it, and gets its credit; it says the pace is a setting, off by
default (#834).
- A Maintenance section covers the PRs that had no entry: #743, #756,
#767, #795, #805, #810, #813, #821, #826, #831.
- The note under the Hermes entry that asked for a runtime bump at
release now says what a remote PC needs.
- `release-summaries.json`: 0.4.7 in en/ko/ja/zh/tr (6 new, 6 improved,
5 fixed). The Turkish lines are not checked by a native speaker.
- `REMOTE_BUNDLE_VERSION` 25 -> 26. Since v0.4.5's runtime the bridge
gained Hermes transcripts (#604), conversation pushes (#689) and
Grok/Antigravity activity (#816), so `remote-v26` is published before
the app release.

Not in this release: #606.

## Validation

- `bun scripts/release-notes.ts 0.4.7` renders the summaries and the
full changelog (235 lines).
- `bun run typecheck` and `bun run build`: pass.
- `TMPDIR=/tmp bun run test:unit`: one failure, `server/voice.test.ts`
("audio.webm" vs "clip.webm"), which fails the same way on unmodified
`main` on this Mac (Bun 1.4.0); CI runs Bun 1.4.2.
- Every PR merged since v0.4.6 was checked against the changelog
section: all 47 are linked.

## Release

After this merges and its CI on `main` passes: push `remote-v26`, wait
for its release, then run the Release workflow with `0.4.7`.
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