Repository navigation
feat(discord): compact workflow notification layout - #6
Merged
Merged
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
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.
Workflow notifications repeat repository, workflow and run information across large field blocks, obscuring the result and failure steps. Use a compact repository author line, one result title, a short job summary and three inline metadata fields; put failed steps first and keep direct run links.
The layout stays within standard Discord Embeds and follows the structure used by established notification actions. Preserve escaping, mention suppression, truncation, rate-limit handling and receipt verification. No Webhooks or Secrets change and no test messages are sent.
Validation: 20 Node tests pass, including the existing safety/delivery tests and new layout/cancellation checks;
git diff --checkpasses. A local success/failure/cancelled comparison preview was generated directly from payloads. Browser visual inspection remains unverified because the browser policy rejects local file URLs; the preview does not establish rendering in the Discord client.