docs(mini_memo): use openvelaClaw brand name and add CI check - #638
Merged
tanghao-xiaomi merged 2 commits intoJul 28, 2026
Conversation
Rename the brand-styled references 'VelaClaw' to 'openvelaClaw' in the mini_memo guide prose. The lowercase code identifiers (velaclaw_client_open, velaclaw_ask, @system.velaclaw) and the VELACLAW_DAEMON macro are the actual framework API and remain unchanged.
Add a lightweight PR check that fails when the CamelCase brand form
'VelaClaw' appears in any Markdown file. The convention is to use
'openvelaClaw' (lowercase 'openvela' prefix, capital 'C') as the brand
name in prose, to reduce trademark risk.
The check is intentionally case-sensitive and does NOT flag:
- lowercase code identifiers: velaclaw, @system.velaclaw,
velaclaw_client_open, velaclaw_ask (real framework APIs)
- uppercase macro: VELACLAW_DAEMON (real Kconfig / macro name)
Note: this check depends on the brand rename in open-vela#636 being merged
first. Otherwise the base branch's existing 'VelaClaw' occurrences
would cause subsequent PRs to fail.
This was referenced Jul 28, 2026
tanghao-xiaomi
merged commit Jul 28, 2026
e0fe84e
into
open-vela:dev-ai-contest-2026
5 checks passed
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.
Summary
Combines two related changes into one PR:
VelaClaw->openvelaClawinmini_memo_guide.md(18 occurrences) to reduce trademark risk. Prefixing with the open-source project nameopenvela(with capitalCinClaw) is a lower-risk brand form than the bareVelaClaw..github/workflows/brand-name-check.yml) that fails any PR reintroducing the CamelCase brand formVelaClawin Markdown, so the convention is enforced going forward.Supersedes #636 and #637.
What is NOT changed (intentional)
These are real framework API / macro names — renaming them would break examples and the actual API surface. The CI check is case-sensitive and does not flag them:
velaclaw,@system.velaclaw,velaclaw_client_open,velaclaw_askVELACLAW_DAEMONRenaming the underlying framework feature (the
velaclawAPI /@system.namespace) is out of scope for this PR and would require a coordinated upstream change.CI check behavior
pull_request(opened / reopened / synchronize).*.mdfiles with a plain case-sensitivegrep.::error file=...,line=...annotations pointing at each offending line, prints a summary that names the allowed form and the identifiers that are intentionally exempt, and fails the job.OKline and passes.ubuntu-latest.Commits
docs(mini_memo): use openvelaClaw brand name to reduce trademark risk— the rename (24 lines changed).ci: add brand-name check for 'VelaClaw' in Markdown— the workflow (46 lines added).The two commits are kept separate so the rename can be reviewed on its own if needed. Merging both together is the intended flow: the rename first cleans the tree, then the CI is enabled to prevent regression.