Repository navigation
feat(discord): improve workflow summary cards - #5
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.
Actions notifications now put the outcome and any failed jobs first, with direct links to failed jobs and their failed steps. Success cards omit zero counts and repeated commit subjects; repository/workflow, PR or branch, linked SHA and execution duration make each result identifiable. Cancelled and unusual outcomes remain distinct.
Duration uses the current attempt's earliest job start and latest completion, not original-run creation, update timestamps or summed parallel job durations. Missing timings stay unavailable. Long failure lists show an explicit omitted count and link to the full run.
The shared implementation applies to ark and arknet. No caller workflow, Secret, Webhook, permissions or delivery retry/receipt contract changes. Metadata escaping and bounded fields retain safe Markdown links and Discord size limits.
Validation: 18 local Node tests passed, including success/failure/cancellation, rerun duration, long Unicode metadata, link boundaries, omission counts, rate limits and redacted delivery errors. Bilingual notification documentation updated. An offline HTML preview uses fictional data; no unsolicited test message was sent and actual Discord rendering has not yet been verified.