stackatdocs

Stackat documentation

On this page

Stackat is a GitHub App for platform teams. It finds the Helm charts, Terraform providers and container images your repositories pin, reads every upstream release note between your version and the latest, and opens one GitHub issue per tool that says what the upgrade means for your files.

What you get#

  • One issue per tool that is behind, labelled stackat, with a verdict (safe to upgrade, review, edits needed, migration), a risk of high, medium or low, and the exact keys and lines a breaking change touches. See How issues work.
  • Pull requests, if you want them: a ready one when nothing in the notes touches your files, a draft with the checklist when something does. See Pull requests.
  • Replies on the issue steer it: /stackpaw pr, /stackpaw ignore, /stackpaw reevaluate and more. See Commands.
  • A dashboard at app.stackat.dev with what to do next, every tool behind, and dated audit evidence. See Dashboard.
  • Slack: urgent security fixes and a weekly digest in your channel. See Slack.
  • Settings in git: one .stackat.yml per repository or for the whole organisation. See .stackat.yml.

Two apps#

AppReadsWritesFor
StackpawYour repositoriesIssues and pull requestsMost teams
Stackpaw AuditYour repositories (code read-only)Issues onlyTeams whose policy forbids a bot changing code

Both scan the same way and open the same issues. Only Stackpaw can open pull requests.

Start here#