Skip to content

feat: add natural multilingual README quality gate - #3

Merged
JNHFlow21 merged 1 commit into
mainfrom
docs/natural-bilingual-readme
Aug 12, 2026
Merged

feat: add natural multilingual README quality gate#3
JNHFlow21 merged 1 commit into
mainfrom
docs/natural-bilingual-readme

Conversation

@JNHFlow21

Copy link
Copy Markdown
Owner

Summary

  • require translated READMEs to read naturally in the target language while preserving semantic parity with the canonical document
  • add a Simplified Chinese-specific quality checklist for headings, terminology, maintainer-only detail, and stale version drift
  • make Repository Pulse output only the linked chart instead of adding a generic GitHub Traffic disclaimer in English or translated READMEs
  • remove the same generic paragraph from this Skill's English and Chinese README

Validation

  • 10 unit tests passed
  • compileall passed
  • strict public-surface and Gitleaks history audit passed
  • forbidden English and Chinese disclaimer sentences are absent
  • git diff --check passed

@JNHFlow21
JNHFlow21 merged commit 80baf1f into main Aug 12, 2026
3 checks passed
@JNHFlow21
JNHFlow21 deleted the docs/natural-bilingual-readme branch August 12, 2026 01:27

@chatgpt-codex-connector chatgpt-codex-connector 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.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6aebd7b7b0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread CHANGELOG.md
All notable changes are documented here. This project follows semantic
versioning for tagged releases.

## [0.1.2] - 2026-08-11

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P2 Badge Update citation metadata for the 0.1.2 release

This declares 0.1.2 as a dated release, but CITATION.cff still advertises version: 0.1.1. If v0.1.2 is tagged from this revision, citation tools and GitHub's citation UI will therefore provide stale release metadata; update the CFF version alongside the changelog, as was done for 0.1.1.

Useful? React with 👍 / 👎.

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