Support disable/enable commands
Open
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 199
- Forks
- 67
- Avg merge
- 6h 24m
- Merged PRs (30d)
- 3
Description
The example from github blog is:
# disable command workflow processing
echo "::stop-commands::`echo -n ${{ github.token }} | sha256sum | head -c 64`"
# log untrusted output
echo "untrusted output"
# enable workflow command processing
echo "::`echo -n ${{ github.token }} | sha256sum | head -c 64`::"
The disable/enable is constant, so they could be provided as actions. Better yet, though, would be a withUntrusted or withCommandsDisabled workflow step that takes other workflow steps as input, and runs then with commands disabled as above.
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
The issue provides a GitHub Actions shell example but names no repository files, tests, or entry points. Start by reviewing how this plugin represents workflow steps and commands, then resolve whether the desired result is standalone disable/enable actions or a step wrapper before defining completion criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100