StackGuardian / StackGuardian/tirith
feat(action): push state automatically via a post-run step
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 165
- Forks
- 42
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
Use the Action's post-run phase (the way actions/checkout runs Post Run actions/checkout@v4) so
the user adds nothing to their pipeline for pushing states after apply. Composite actions have no
native post:, so this likely means promoting the Action to a node wrapper with post: (or a
documented second step). Provide the GitLab and Bitbucket equivalents (after_script /
after-script) in the respective integrations.
Acceptance. A workflow that applies and never mentions state still gets its masked state pushed
by the post-run step; GitLab/Bitbucket recipes documented.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the existing Action entry point and its current apply/state-push flow, then compare the post-run behavior of actions/checkout. Check the GitLab and Bitbucket integration recipes for their after_script and after-script equivalents; done means apply-only workflows push masked state automatically and both recipes are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100