caezium/Sentry → GitHub Issues
File a deduplicated GitHub issue (with stack trace) for each new Sentry issue. No Sentry Business plan needed.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| sentry_org | Sentry organization slug. | yes | — |
| sentry_projects | Space-separated Sentry project slug(s) to watch. | yes | — |
| sentry_auth_token | Sentry read-only auth token. Scopes: project:read, event:read, org:read. | yes | — |
| sentry_host | Sentry base URL. Set this for a self-hosted Sentry. | no | https://sentry.io |
| query | Sentry issue search query. | no | is:unresolved |
| lookback_hours | Only file issues first seen within this many hours. | no | 24 |
| max_per_run | Maximum issues to create per run (backlog guard). | no | 25 |
| label | Label applied to filed issues. Created if missing; also used for dedup. | no | sentry |
| repo | Target repo (owner/name) to file issues in. | no | ${{ github.repository }} |
| github_token | GitHub token with issues:write on the target repo. | no | ${{ github.token }} |
Outputs
no outputs