sarisia/actions-status-discord

Post GitHub Actions status to Discord as an beautiful embed

🍜 Fu Takakazu (a.k.a Sarisia)

📝 Recent Blog Posts

• Oct 12 - Gmail から iCloud カスタムドメインメールを扱えなかった
• May 16 - ブラウザだけでOS自作入門しよう
• Mar 29 - Docker ではじめる "ゼロからのOS自作入門"
• Feb 24 - docker-compose の bind mount を1行で書くな
• Jan 29 - GitHubへのヤバいソースコードのお漏らしを発見する方法を夢の中で考えてみる

Generated with sarisia/actions-readme-feed & GitHub Actions

🔤 Natural Languages

• 🇯🇵 Japanese
• 🇺🇸 English
• 🇨🇳 Chinese (Simplified)

🔗 Links

• Portfolio (sarisia.cc)
• Blog (note.sarisia.cc)
• Zenn (zenn.dev/sarisia)
• Qiita (qiita.com/sarisia)
• Twitter (twitter.com/A1ces)

Related Repositories

• Neuenmuller - Forks of OSS projects

actions-status-discord's Issues

improve devcontainer ci

pin action versions to specific sha in release workflow

Have a way to override the `fields` embed (or at least the `eventDetail` part of the fields)

Hi !

It would be cool if there was a way to override the fields part of the embed.

I really like the display of the message when using fields but, sometimes, the eventDetail part is huge (when squash merging a PR with lots of commits, github's default is to append all the commit message to the merge commit message).

Currently, there is no way to reproduce the display of what the fields embed do and passing nocontext remove the fields entirely.

What do you think about adding an option which, when provided, override the eventDetail value ?

---

Something event more flexible would be to be able to pass an option with the entire fields array but I'm not sure if it's possible to passe something like:

with:
  fields: ${{ fromJSON('[{"name":"Repository","value":"...","inline":true},{"name":"Ref","value":"...","inline":true},{"name":"Event","value":"...","inline":false},{"name":"Triggered by","value":"...","inline":true},{"name":"Workflow","value":"...","inline":true}]') }}

accept multiple webhook endpoints

add markdown example in readme

dump result payloads

ci: e2e-all-os is not working

Add GitHub Actions build log to release assets

GitHub Actions only keeps the build log for 90 days at max,
so we need to add these logs (build proof) to the release assets.

Is it possible to add related links such as storybooks and production links (staging links) to Discord comments?

Is there a way to send a file to Discord with this action?

add src tag in release workflow

since release workflow force updates versioned git tag

README is missing in marketplace page

maybe we shouldn't use automatic release action...

I'm not seeing how this works, can you help?

I'm newer to github actions and I'm just not seeing where/how the scripts runs so I can look at the javascript that is actually running.

In actions.yml it says:

runs:
  using: "node20"
  main: "lib/index.js"

I don't see /lib/index.js anywhere in the project directory, where is this file being called from? -- I'm interested in looking at the js itself to see what's happening and try to learn from it.

fix e2e in release workflow

• do not use v1 tag
• use upload-artifact and download-artifact
  • since we cannot build this action with devcontainer in macos (macos runner does not have docker!)
  • maybe checking out the tag ref is log easier

char limit checks are really slack currently

use devcontainer image in ci

• use devcontainer-cli to build & publish devcontainer image
• use that devcontainer image in devcontainer.json AND GitHub Actions Workflows

Customizable description

This workflow currently runs for us to notify of a push to a branch. The description shows the title of that PR, but it would be ideal if we could list the title of each commit included with that PR. Currently looking into what data you are getting back from github and if this is even an option, but figured I would toss it here if anyone knows of a better way to accomplish this. Great action.

add workflow run reference to release commit

update build-and-tag-action

Tag user or role on discord

Discussed in #387

^{Originally posted by murilomorato December 15, 2022}
I created a server to receive alerts whenever a deploy fails, but I haven't been receiving notifications alerts.
I tried to insert inside the 'description' prop my Role tag and my user id. They arrive tagged in the discord message, but it does not generate the notification, as I believe the message arrives as a kind of 'quote', not as a normal message.

Have you tried any alternatives yet?

Thanks😉

⚠️ This action has a security risk! Release source/change diff is obfuscated

SSIA

Ref: v1.10.0...v1.10.1

This seems weird, there is no way to validate what it is in this upgrade from a technical and security perspective. I've currently closed all dependabot upgrade requests because of it.

../Frenck

feature request: posting into Discord's thread

I would like to post into Discord's thread by this action.
The URL format is https://discord.com/api/webhooks/{webhook_id}/{webhook.token}?thread_id={thread_id}.

question

Hi.

Are it's possible to set ${{ job.status }} - so It will display on actions, if it has been success or failed?

Because it does not work for me. ;/

How to delete previous messages?

Any way to delete previous messages in a channel before post a new one?

warn /github suffix

Your .dependabot/config.yml contained invalid details

Dependabot encountered the following error when parsing your .dependabot/config.yml:

Automerging is not enabled for this account. You can enable it from the [account settings](https://app.dependabot.com/accounts/sarisia/settings) screen in your Dependabot dashboard.

Please update the config file to conform with Dependabot's specification using our docs and online validator.

Suggestion: status-defined image and descriptions

Hello,
I'm unable to do this myself, but a suggestion I have and would appreciate if implemented, is enabling the option to have a custom image and description per status, for success, cancellation and failure.

I've partially hardcoded this on my own fork to create the following real world example:

auto release workflow

support `skipped` for status

to enable reporing step status

https://docs.github.com/en/actions/learn-github-actions/contexts#steps-context

Workflow link points to a non-existent commit on pull requests

Issue description

For workflows triggered by pull_request events, the workflow link points to a commit that does not belong to the repository.

For example,

the link above goes to https://github.com/GiganticMinecraft/SeichiAssist/commit/695bf7133c95640b663f4e817f84f300874ca809/checks, while I expect it to go to https://github.com/GiganticMinecraft/SeichiAssist/commit/2cb1b549800285c790832a45d71e17e21fd85faf/checks.

I believe the link uses SHA hash of a merge commit automatically generated by Actions, which is different from github.sha.
EDIT: My bad, this is in fact the expected github.sha, but would it be reasonable to use github.event.pull_request.head.sha when this is available?

Reproduction

Set up a workflow with sarisia/actions-status-discord@v1, trigger it with pull_request event and check the link generated for "Workflow" column.

Full workflow file

add CONTRIBUTING.md

I just forgot how to release this action

review workflow permissions