fix(issues): Remove confusion phrasing around merges#16621
Open
fix(issues): Remove confusion phrasing around merges#16621
Conversation
This phrasing is likely outdated or was confusingly worded - merging is supported for all error issues so let's just clean it up.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
lobsterkatie
added a commit
that referenced
this pull request
Feb 28, 2026
We're removing the bit about DIFs and sourcemaps from the more general "only error issues" include[1], so this replaces the include on the reprocessing page with a note which still includes that information (reworded a bit for clairity). [1] #16621
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This phrasing is likely outdated or was confusingly worded - merging is supported for all error issues so let's just clean it up.