Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ No related issue: <reason>
The reason is required. Write the escape without backticks: the gate masks
inline code spans before matching, so a backticked escape is invisible to it
and the PR draws the advisory `needs-issue-linkage` label anyway. The linkage
rule is advisory: the `check-contract` step inside `ci-status` leaves a comment and
rule is advisory: the `check-contract` step inside `CI Status` leaves a comment and
the `needs-issue-linkage` label instead of failing. That step's output reports
the exact rule it applied and is authoritative over this comment.

Expand Down
2 changes: 1 addition & 1 deletion CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ A repository's own `CONTRIBUTING.md`, with project-specific details, overrides t
3. Ensure the project builds and its checks pass locally.
4. Open a pull request, fill out the template, and link the related issue.
- Title it in [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) form with a standard type, `<type>[optional scope]: <description>`, for example `feat(api): add pagination`. The title becomes the squash-merge commit subject on the default branch.
- Where the repository enforces this, the `ci-status` check reports on your pull request and must pass before merge.
- Where the repository enforces this, the `CI Status` check reports on your pull request and must pass before merge.
5. Address review feedback. Pull requests are squash-merged once every review thread is resolved and any required checks pass.

## Reporting security issues
Expand Down
Loading