Skip to content

Commit db0f59b

Browse files
vividctrlaltvividctrlalt
authored
Merge pull request #3 from vividctrlalt/prcheck2
ci: enhance PR lint with stricter title and scope checks
2 parents e6b4bff + 8d83788 commit db0f59b

2 files changed

Lines changed: 144 additions & 41 deletions

File tree

‎.github/workflows/pr-check.yml‎

Lines changed: 55 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -15,55 +15,82 @@ jobs:
1515
runs-on: ubuntu-latest
1616

1717
steps:
18-
- name: Check PR title format
18+
- name: Validate PR title and description
1919
uses: actions/github-script@v7
2020
with:
2121
script: |
2222
const title = context.payload.pull_request.title;
23-
23+
const body = context.payload.pull_request.body;
2424
const errors = [];
25+
const warnings = [];
26+
27+
const allowedTypes = ['feat','fix','refactor','docs','style','test','chore','ci','perf','build','revert'];
28+
const knownScopes = [
29+
'framework','chainbase','actuator','consensus','common','crypto','plugins','protocol',
30+
'net','db','vm','tvm','api','jsonrpc','rpc','http','event','config',
31+
'block','proposal','trie','log','metrics','test','docker','version',
32+
'freezeV2','DynamicEnergy','stable-coin','reward','lite','toolkit'
33+
];
2534
26-
// Title should not be empty or too short
35+
// 1. Title length check
2736
if (!title || title.trim().length < 10) {
2837
errors.push('PR title is too short (minimum 10 characters).');
2938
}
30-
31-
// Title should not exceed 72 characters
32-
if (title.length > 72) {
39+
if (title && title.length > 72) {
3340
errors.push(`PR title is too long (${title.length}/72 characters).`);
3441
}
3542
36-
// Title should follow conventional format: type: description
37-
// Allowed types: feat, fix, refactor, docs, style, test, chore, ci, perf, build, revert
38-
const conventionalRegex = /^(feat|fix|refactor|docs|style|test|chore|ci|perf|build|revert)(\(.+\))?:\s.+/;
39-
if (!conventionalRegex.test(title)) {
43+
// 2. Conventional format check
44+
const conventionalRegex = /^(feat|fix|refactor|docs|style|test|chore|ci|perf|build|revert)(\([^)]+\))?:\s.+/;
45+
if (title && !conventionalRegex.test(title)) {
4046
errors.push(
41-
'PR title must follow conventional format: `type: description`\n' +
42-
'Allowed types: feat, fix, refactor, docs, style, test, chore, ci, perf, build, revert\n' +
43-
'Example: `feat: add new transaction validation`'
47+
'PR title must follow conventional format: `type(scope): description`\n' +
48+
' Allowed types: ' + allowedTypes.map(t => `\`${t}\``).join(', ') + '\n' +
49+
' Example: `feat(tvm): add blob opcodes`'
4450
);
4551
}
4652
47-
if (errors.length > 0) {
48-
const message = '### PR Title Check Failed\n\n' + errors.map(e => `- ${e}`).join('\n');
49-
core.setFailed(message);
50-
} else {
51-
core.info('PR title format is valid.');
53+
// 3. No trailing period
54+
if (title && title.endsWith('.')) {
55+
errors.push('PR title should not end with a period (.).');
5256
}
5357
54-
- name: Check PR description
55-
uses: actions/github-script@v7
56-
with:
57-
script: |
58-
const body = context.payload.pull_request.body;
58+
// 4. Description part should not start with a capital letter
59+
if (title) {
60+
const descMatch = title.match(/^\w+(?:\([^)]+\))?:\s*(.+)/);
61+
if (descMatch) {
62+
const desc = descMatch[1];
63+
if (/^[A-Z]/.test(desc)) {
64+
errors.push('Description should not start with a capital letter.');
65+
}
66+
}
67+
}
68+
69+
// 5. Scope validation (warning only)
70+
if (title) {
71+
const scopeMatch = title.match(/^\w+\(([^)]+)\):/);
72+
if (scopeMatch && !knownScopes.includes(scopeMatch[1])) {
73+
warnings.push(`Unknown scope \`${scopeMatch[1]}\`. See CONTRIBUTING.md for known scopes.`);
74+
}
75+
}
5976
77+
// 6. PR description check
6078
if (!body || body.trim().length < 20) {
61-
core.setFailed(
62-
'### PR Description Check Failed\n\n' +
63-
'PR description is too short or empty. Please describe what this PR does and why.'
64-
);
79+
errors.push('PR description is too short or empty (minimum 20 characters). Please describe what this PR does and why.');
80+
}
81+
82+
// Output warnings
83+
for (const w of warnings) {
84+
core.warning(w);
85+
}
86+
87+
// Output result
88+
if (errors.length > 0) {
89+
const docLink = 'See [CONTRIBUTING.md](https://github.com/' + context.repo.owner + '/' + context.repo.repo + '/blob/develop/CONTRIBUTING.md#pull-request-guidelines) for details.';
90+
const message = '### PR Lint Failed\n\n' + errors.map(e => `- ${e}`).join('\n') + '\n\n' + docLink;
91+
core.setFailed(message);
6592
} else {
66-
core.info('PR description is valid.');
93+
core.info('PR lint passed.');
6794
}
6895
6996
build:

‎CONTRIBUTING.md‎

Lines changed: 89 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,8 @@ Here are some guidelines to get started quickly and easily:
1616
- [Commit Messages](#Commit-Messages)
1717
- [Branch Naming Conventions](#Branch-Naming-Conventions)
1818
- [Pull Request Guidelines](#Pull-Request-Guidelines)
19+
- [PR Title Format](#PR-Title-Format)
20+
- [PR Description](#PR-Description)
1921
- [Special Situations And How To Deal With Them](#Special-Situations-And-How-To-Deal-With-Them)
2022
- [Conduct](#Conduct)
2123

@@ -165,15 +167,70 @@ Template:
165167
The message header is a single line that contains succinct description of the change containing a `commit type`, an optional `scope` and a subject.
166168
167169
`commit type` describes the kind of change that this commit is providing:
168-
* feat (new feature)
169-
* fix (bug fix)
170-
* docs (changes to documentation)
171-
* style (formatting, missing semi colons, etc. no code change)
172-
* refactor (refactoring production code)
173-
* test (adding or refactoring tests. no production code change)
174-
* chore (updating grunt tasks etc. no production code change)
175170
176-
The `scope` can be anything specifying place of the commit change. For example:`protobuf`,`api`,`test`,`docs`,`build`,`db`,`net`.You can use * if there isn't a more fitting scope.
171+
| Type | Purpose | Example |
172+
|------|---------|---------|
173+
| `feat` | New feature | `feat(tvm): add blob opcodes` |
174+
| `fix` | Bug fix | `fix(db): improve resource management` |
175+
| `docs` | Documentation only | `docs: fix formatting issues in README` |
176+
| `style` | Code style (no logic change) | `style: fix import order and line length` |
177+
| `refactor` | Code refactoring (no behavior change) | `refactor(config): simplify parameters` |
178+
| `test` | Adding or updating tests | `test(vm): add unit tests for opcodes` |
179+
| `chore` | Build tooling, dependencies, etc. | `chore(version): bump to v4.7.8` |
180+
| `ci` | CI/CD configuration | `ci: add PR check workflow` |
181+
| `perf` | Performance improvement | `perf(trie): optimize query performance` |
182+
| `build` | Build system changes | `build: add aarch64 support for RocksDB` |
183+
| `revert` | Reverting a previous commit | `revert: restore ApiUtilTest.java` |
184+
185+
The `scope` is optional and specifies the place or module of the commit change.
186+
187+
#### Module Scopes
188+
189+
| Scope | Description |
190+
|-------|-------------|
191+
| `framework` | Core framework, services, APIs, RPC interfaces |
192+
| `chainbase` | Blockchain storage, state management, database layer |
193+
| `actuator` | Transaction execution engine, smart contract operations |
194+
| `consensus` | Consensus mechanism (DPoS, PBFT) |
195+
| `common` | Common utilities, configuration, shared infrastructure |
196+
| `crypto` | Cryptographic functions, key management, signatures |
197+
| `plugins` | Node tools (Toolkit, ArchiveManifest, database plugins) |
198+
| `protocol` | Protocol definitions, protobuf messages, gRPC contracts |
199+
200+
#### Functional Domain Scopes
201+
202+
| Scope | Description | Example |
203+
|-------|-------------|---------|
204+
| `net` | P2P networking, message handling, peer sync | `feat(net): optimize sync logic` |
205+
| `db` | Database operations, queries, persistence | `fix(db): handle null pointer in query` |
206+
| `vm` / `tvm` | Virtual machine, bytecode execution, EIP impl | `feat(tvm): implement eip-7823` |
207+
| `api` | HTTP/gRPC API endpoints | `fix(api): handle null response` |
208+
| `jsonrpc` | JSON-RPC interface (Ethereum-compatible) | `fix(jsonrpc): support blockHash param` |
209+
| `rpc` | gRPC services and methods | `fix(rpc): handle timeout correctly` |
210+
| `http` | HTTP server and endpoints | `feat(http): add new endpoint` |
211+
| `event` | Event logging and event service | `feat(event): optimize concurrent writes` |
212+
| `config` | Configuration management, feature flags | `refactor(config): simplify parameters` |
213+
| `block` | Block processing, validation, structure | `fix(block): validate block header` |
214+
| `proposal` | On-chain governance proposals | `feat(proposal): add Osaka proposal` |
215+
| `trie` | Merkle tree, state trie operations | `perf(trie): optimize tree query` |
216+
| `log` | Application logging | `refactor(log): reduce noise` |
217+
| `metrics` | Performance monitoring, Prometheus | `feat(metrics): add Prometheus support` |
218+
| `test` | Test infrastructure and utilities | `test(proposal): add unit test cases` |
219+
| `docker` | Docker containerization and deployment | `feat(docker): add ARM64 support` |
220+
| `version` | Version and release management | `chore(version): bump to v4.7.8` |
221+
222+
#### Feature Scopes
223+
224+
| Scope | Description |
225+
|-------|-------------|
226+
| `freezeV2` | Resource delegation / freeze-unfreeze V2 mechanism |
227+
| `DynamicEnergy` | Dynamic energy pricing mechanism |
228+
| `stable-coin` | Stable coin features and operations |
229+
| `reward` | Block producer rewards distribution |
230+
| `lite` | Lite fullnode functionality |
231+
| `toolkit` | Node maintenance tools (Toolkit.jar) |
232+
233+
You can use `*` if there isn't a more fitting scope.
177234
178235
The subject contains a succinct description of the change:
179236
1. Limit the subject line, which briefly describes the purpose of the commit, to 50 characters.
@@ -204,13 +261,32 @@ If the purpose of this submission is to modify one issue, you need to refer to t
204261
4. Use `feature/` as the prefix of the `feature` branch, briefly describe the feature in the name, and connect words with underline (e.g., feature/new_resource_model, etc.).
205262
### Pull Request Guidelines
206263
264+
#### PR Title Format
265+
266+
PR titles must follow the conventional commit format and will be checked by CI:
267+
268+
```
269+
type(scope): description
270+
```
271+
272+
| Rule | Requirement |
273+
|------|-------------|
274+
| Format | `type: description` or `type(scope): description` |
275+
| Length | 10 ~ 72 characters |
276+
| Type must be one of | `feat` `fix` `refactor` `docs` `style` `test` `chore` `ci` `perf` `build` `revert` |
277+
278+
#### PR Description
279+
280+
- PR description must not be empty, minimum **20 characters**.
281+
- Should explain **what** the PR does and **why**.
282+
283+
#### General Rules
284+
207285
1. Create one PR for one issue.
208286
2. Avoid massive PRs.
209-
3. Write an overview of the purpose of the PR in its title.
210-
4. Write a description of the PR for future reviewers.
211-
5. Elaborate on the feedback you need (if any).
212-
6. Do not capitalize the first letter.
213-
7. Do not put a period (.) in the end.
287+
3. Elaborate on the feedback you need (if any).
288+
4. Do not capitalize the first letter of the description.
289+
5. Do not put a period (.) at the end of the title.
214290
215291
216292

0 commit comments

Comments
 (0)