Skip to content

feat: implement dual-mode export with build tags separation #56

feat: implement dual-mode export with build tags separation

feat: implement dual-mode export with build tags separation #56

Re-run triggered November 10, 2025 01:18
Status Failure
Total duration 10s
Artifacts

pr-title-checker.yml

on: pull_request
pr title lint
5s
pr title lint
Fit to window
Zoom out
Zoom in

Annotations

1 error
pr title lint
Title "implement dual-mode export with build tags separation(#35)" does not conform to the standard. Found the following issues: - Title format is incorrect. It should be: <type>(<scope>): <subject> - Type must be one of: feat, fix, docs, style, refactor, test, perf, build, ci, chore, revert - Scope format is incorrect. Scope should only contain letters, numbers, hyphens, and underscores Examples of correct title format: - feat(prom): add router for prom module - ci: change pr lint pattern - feat(good): good Title Restrictions: The format for a PR (Pull Request) title should follow these rules: <type>(<scope>): <subject> type and subject are required fields. scope is optional and can be omitted. Character Limit: The subject must not exceed 120 characters. Type Restrictions: the type must be one of the following specified options: feat, fix, docs, style, refactor, test, perf, build, ci, chore, revert Character Restrictions: the title may only contain ASCII characters; other character sets are not allowed. Whitespace Rules: the subject must not end with a space; there must be only one space following the `:`