ci(frontend-deploy): name what is being deployed - #8431
Closed
talissoncosta wants to merge 1 commit into
Closed
Conversation
The cards identified a deploy by short sha, which says nothing about what is in it. Adds the pull request title under the headline, linked to the pull request. No API call is needed. A squash merge puts the title and number in the first line of the commit message, as "title (#123)", and all of the last forty commits on main match that. A direct push or a merge commit will not, so the number is optional and the title falls back to the whole line unlinked. The title goes full width as a context line rather than into the field grid, which is two narrow columns and would wrap a real title badly. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub. 3 Skipped Deployments
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #8431 +/- ##
=======================================
Coverage 98.81% 98.81%
=======================================
Files 1621 1621
Lines 66118 66118
=======================================
Hits 65334 65334
Misses 784 784 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
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.
Thanks for submitting a PR! Please check the boxes below:
docs/if required so people know about the feature.Changes
The deploy cards identify a deploy by short sha, which tells you nothing about what is in it. This adds the pull request title under the headline, linked to the pull request.
No API call and no extra permission. A squash merge puts the title and number in the first line of the commit message as
title (#123), and all forty of the last forty commits onmainmatch that shape. A direct push or a merge commit will not, so the number is optional: the title then falls back to the whole first line, unlinked, rather than producing a broken link.The title goes full width as a
contextblock rather than into the field grid, which is two narrow columns and would wrap a real title badly.Deploying
Deployed
How did you test this code?
The parsing, against five commit message shapes:
refactor(styles): diff view and code theme on shared tokens (#8069)/pull/8069chore: a direct push with no pull request/pull/8420fix: mentions (#123) mid-sentence and ends plainlyThat last case is why the pattern is anchored to the end of the line.
The rendering, across all four states with and without a title, confirming the
contextblock appears only when there is one and the block order is otherwise unchanged:Both files parse as YAML. Not exercised end to end, since this workflow only runs on push to
main. The steps arecontinue-on-error: true, so nothing here can hold up or fail a deploy.