-
Notifications
You must be signed in to change notification settings - Fork 76
fix(rel): unify changelog caps #1061
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.
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
docs/technical-changelog.mdx
Outdated
| - Clean up cmd leak `(PR #3642)` | ||
| - A few bugfixes for the experimental commit search on searcher `(PR #3639)` | ||
| - Close diff reader `(PR #3636)` | ||
| - A few small fixes for commit search on searcher experiment `(PR #3620)` | ||
| - Nightly Minor Release Pipeline `(PR #3609)` | ||
| - NA | ||
| - /latest releaseregistry endpoint returns latest by semver `(PR #3563)` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe this is a misspellling or something? seems like releaseregistry should be 1 word
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a service name, and we generally refer to it as one word for some reason 🤷 😆
But really, it shouldn't be in there at all as it's an internal service 👀
Looks like despite being N/A in the changelog for a few of these, the author forgot to add the no-changelog label so it was still included. I cleaned up the rest of these as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ah cool!
7427025 to
6974fd9
Compare

Unify capitalization for changelog bullets
Pull Request approval
You will need to get your PR approved by at least one member of the Sourcegraph team. For reviews of docs formatting, styles, and component usage, please tag the docs team via the #docs Slack channel.