Skip to content

๐Ÿ”ด๐Ÿ“œ Use smee.io to debug GitHub Action runs

Notifications You must be signed in to change notification settings

re-actors/smee-action

ย 
ย 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

ย 

History

15 Commits
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 
ย 

Repository files navigation

Smee Action

Use smee.io to debug Action runs

Usage

workflow "Smee!" {
  on = "push"
  resolves = ["test"]
}

# Place this Action early in your workflow
action "smee" {
  uses = "JasonEtco/smee-action@master"
}

action "test" {
  needs = ["smee"]
}

โš ๏ธ

Heads up! This is only to be used for debugging, not for sensitive data. Smee.io is not secured by any authentication, so anyone with the channel ID can view your payloads as they come in.


Seeing the payloads

A common misconception about Smee.io is that the payloads will be available all the time - to see a new payload as its sent, you must have a browser tab open to the channel URL. The payloads are stored in localStorage in your browser.

Specifying the channel

By default, this Action will post event payloads to the smee.io/REPOSITORY_ID - if you aren't sure what that is, it'll log it for you the first time you run the Action.

You can specify what channel you want to send to:

# Using arguments
action "smee" {
  uses = "JasonEtco/smee-action@master"
  args = "--channel my-channel"
}

# Using a secret
action "smee" {
  uses = "JasonEtco/smee-action@master"
  secrets = ["SMEE_CHANNEL"]
}

About

๐Ÿ”ด๐Ÿ“œ Use smee.io to debug GitHub Action runs

Resources

Stars

Watchers

Forks

Packages

No packages published

Languages

  • JavaScript 77.7%
  • Dockerfile 19.5%
  • HCL 2.8%