Docs: don't pass a prompt between jobs through a job output
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 86/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, markdown
- Domain
- documentation
Research direction
Open CLAUDE.md and find the "Usage by Consuming Repositories" section; the whole change is a short gotcha added there. Read it alongside #70 to see how consumers pass needs.<job>.outputs into the executor, so the wording matches the existing guidance. Done when the section states both points: build the prompt in the job that calls the executor or pass it as an (encrypted) artifact, and never route untrusted multi-KB text through job outputs.
Written by the indexing model from the issue text.
Description
GitHub Actions drops any job output whose value the runner's secret masker would mask. The masker matches more than secret values: it also matches patterns such as Bearer <token-like word>. A consumer that builds prompt in an earlier job and passes it to an ai-workflows executor through needs.<job>.outputs can lose the whole prompt this way. The runner shows only a warning, the executor receives an empty string, and the run can still go green.
This is what broke dotCMS/core's autodoc. Any issue or PR text containing an example such as curl -H "Authorization: Bearer ..." tripped the masker. Job outputs are also capped at 1 MB per job.
Fix: add a short gotcha under "Usage by Consuming Repositories" in CLAUDE.md:
- Build the prompt in the same job that calls the executor, or pass large or untrusted text as an artifact (encrypted, if the repo is public).
- Never route untrusted, multi-KB text through job outputs.
Raised in review of #70.
- Dominant language
- No language data
- Stars
- 1
- Forks
- 0
- Avg merge
- 16m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from dotCMS/ai-workflows
-
enhancement
Difficulty 1/5 Under an hour Newbie friendliness 85/100
dotCMS/ai-workflows#74 · 1 comment ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
dotCMS/ai-workflows#72 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
dotCMS/ai-workflows#42 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
dotCMS/ai-workflows#35 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 30/100
dotCMS/ai-workflows#75 ·
All issues in dotCMS/ai-workflows
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
dbt-msft/dbt-sqlserver#897 ·
Maintainers usually reply within 1 day
-
area:docs area:stdlib found-by:duet-audit kind:docs-drift
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
InauguralSystems/EigenScript#2251 · 1 comment ·
Maintainers usually reply within 1 day
-
documentation
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
ivopogace/opencode-courier#422 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
beyondgrep/ack3#413 ·
-
Isaac workingOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
seedds/nxnative#763 · 1 comment ·
Maintainers usually reply within 1 day