Skip to content

CONTRIBUTING.md: minor text tweaks for linters #8533

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
dfawley merged 1 commit into from
Aug 22, 2025
Merged

CONTRIBUTING.md: minor text tweaks for linters #8533

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -75,7 +75,7 @@ smoothly and quickly.
GitHub, which will trigger a GitHub Actions run that you can use to verify
everything is passing.

- Note that there are two github actions checks that need not be green:
- Note that there are two GitHub actions checks that need not be green:

1. We test the freshness of the generated proto code we maintain via the
`vet-proto` check. If the source proto files are updated, but our repo is
Expand Down Expand Up @@ -112,7 +112,7 @@ smoothly and quickly.
- **Does this PR relate to an open issue?** On the first line, please use the
tag `Fixes #<issue>` to ensure the issue is closed when the PR is merged. Or
use `Updates #<issue>` if the PR is related to an open issue, but does not fix
it. Consider filing an issue if one does not already exist.
it. Consider filing an issue if one does not already exist.

- PR descriptions *must* conclude with **release notes** as follows:

Expand All @@ -136,11 +136,11 @@ smoothly and quickly.
* be as short as possible to describe the change being made.

If a PR is *not* end-user visible -- e.g. a cleanup, testing change, or
github-related, use `RELEASE NOTES: n/a`.
GitHub-related, use `RELEASE NOTES: n/a`.

### PR Process

- Please **self-review** your code changes before sending your PR. This will
- Please **self-review** your code changes before sending your PR. This will
prevent simple, obvious errors from causing delays.

- Maintain a **clean commit history** and use **meaningful commit messages**.
Expand Down