Skip to content
slack

update docs on how to get metadata #102

Sign in to view logs

update docs on how to get metadata

update docs on how to get metadata #102

Triggered via issue February 6, 2025 10:01
@david-lunadavid-luna
opened #4451 4752c48
Status Success
Total duration 1m 34s
Artifacts –

slack.yml

on: issues
slack
1m 24s
slack
Fit to window
Zoom out
Zoom in

Annotations

6 warnings
slack
Failed to download action 'https://api.github.com/repos/slackapi/slack-github-action/tarball/485a9d42d3a73031f12ec201c457e2162c45d02d'. Error: Response status code does not indicate success: 504 (Gateway Timeout).
slack
Back off 23.947 seconds before retry.
slack
Failed to download action 'https://api.github.com/repos/slackapi/slack-github-action/tarball/485a9d42d3a73031f12ec201c457e2162c45d02d'. Error: Response status code does not indicate success: 504 (Gateway Timeout).
slack
Back off 25.125 seconds before retry.
slack
The top-level `text` argument is missing in the request payload for a chat.postMessage call - It's a best practice to always provide a `text` argument when posting a message. The `text` is used in places where the content cannot be rendered such as: system push notifications, assistive technology such as screen readers, etc.
slack
Additionally, the attachment-level `fallback` argument is missing in the request payload for a chat.postMessage call - To avoid this warning, it is recommended to always provide a top-level `text` argument when posting a message. Alternatively, you can provide an attachment-level `fallback` argument, though this is now considered a legacy field (see https://api.slack.com/reference/messaging/attachments#legacy_fields for more details).