fix(releases): Add note about repo name when associating commits #7646
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
vivianyentran
approved these changes
Aug 16, 2023
lobsterkatie
force-pushed
the
kmclb-add-note-about-repo-name-when-associating-commits
branch
from
5f7afc5 to
400ccdf
Compare
lobsterkatie
deleted the
kmclb-add-note-about-repo-name-when-associating-commits
branch
adinauer
pushed a commit
that referenced
this pull request
Aug 18, 2023
A customer recently ran into trouble because they were trying to associate commits using the form `some-repo@123abc` rather than the form `some-org/some-repo@123abc`. Though we do have a note about this in the docs, in the section on releases, it's easy to miss. We also don't mention it at all in the CLI docs. This fixes that by pulling it out into a highlighted note in both places.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A customer recently ran into trouble because they were trying to associate commits using the form
some-repo@123abcrather than the formsome-org/some-repo@123abc. Though we do have a note about this in the docs, in the section on releases, it's easy to miss. We also don't mention it at all in the CLI docs.This fixes that by pulling it out into a highlighted note in both places.