Home Search Pricing Get inErrata About

Sign in Sign up

Graph/ci-output-and-permission-assumption

AntiPattern

CI Workflow Output Misuse

ci-output-and-permission-assumption

Workflow context and artifact/publish metadata get lost or misapplied because step outputs, required CLI flags, and token permissions are assumed implicitly; downstream jobs then can’t reference generated values or bind published packages correctly.

Node Details

Public graph metadata

Updated6/28/2026

Connections

30 linked nodes

MATCHESSolution

Avoid barrel file approaches because they can increase circular dependency issues

MATCHESSolution

Use a published package or configure the workspace to expose only the public API and dist output

MATCHESSolution

passing health checks but its Bash cutover and post-cutover verification scripts exited early or misreported failure — Bash cutover and post-cutover verification scripts. Tension: post-increment arithmetic such as `((elapsed++))` / `((PASS_COUNT++))`, brittle command-output parsing for npm preflight status, and exact JSON-shape assumptions for RPC verification.

MATCHESSolution

This can apparently be fixed by instead using, though I have not tested it: — Run ad-m/github-push-action@v0.5.0. Tension: The problem was that the workflow declared the safe directory outside of the docker containter. Outcome: I opted to avoid the workaround and use an alternative deployment, official gh-pages deployment.

MATCHESSolution

CI Stability Fix. Tension: workflow randomly fails at times. Outcome: xcodebuild -downloadPlatform iOS || echo "⚠️ Platform already installed or download failed, continuing...".

MATCHESSolution

I also usually add a prefix to the artifact name — Upload Build Artifact. Outcome: env: ARTIFACTS_PREFIX: wf-${{ github.workflow_sha }}-${{ github.run_number }}.

MATCHESSolution

consider adding some inputs to the upload action — Upload Build Artifact. Tension: artifact not found for name: build.

MATCHESSolution

you have to make the deploy a job in the same workflow — CI - Build & Test.

MATCHESSolution

I would skip the GitHub Actions artifact steps entirely — After you do “previous steps” in your first job. Outcome: commit/push changes to a separate branch or to the same Git branch.

MATCHESSolution

You need to use artifacts in order to achieve what you are trying to do — between 2 jobs. Tension: There is no persistance of data by default between 2 jobs. Outcome: storing-and-sharing-data-from-a-workflow.

MATCHESSolution

I have to run with the extra `--artifact-server-path /tmp/artifacts` — act -j build-and-deploy -W .github/workflows/deploy_frontend.yml. Tension: it solves it. Outcome: Complete run command.

MATCHESSolution

Use a scheduled workflow to collect workflow run statuses from all repositories and update a dashboard in the organization's README

MATCHESSolution

Is it possible to use `gh workflows run "workflow-name" --ref "pr-branch-name"` to trigger a CI that is not yet in the default branch? — `gh workflows run "workflow-name" --ref "pr-branch-name"`. Tension: today I can only trigger workflows that are already in the default branch. Outcome: I had the same problem using curl.

MATCHESSolution

If you modify an existing workflow on a branch, this modified version will not interfere with workflow runs on your main branch or any other feature branches. — The workflows are active in that the workflows are triggered based on github push events of existing and other repos. Tension: If you create a new workflow on a branch, you will not be able to run it until you merge it into the main branch. Outcome: you will need to merge a minimal version of this workflow with the features you need (e.g. trigger types) to the main branch and then keep modifying it on a new branch.

MATCHESSolution

If you want to always enforce the e2e tests to run. Outcome: you should be able to remove the check for `github.event_name == 'workflow_dispatch'`.

MATCHESSolution

Error: Unable to process file command 'output' successfully. Error: Invalid format ' "build_dir1": {'. Outcome: The GitHub Output is expecting the JSON to be on a single line.

MATCHESSolution

When I push a commit to a MR branch, the workflow is executed twice, both for `push` and `pull_request`. Tension: The workflow includes several jobs of which one them should only run for `pull_request`. Outcome: Maybe a bit late, but you could use Concurrency:.

MATCHESSolution

Either adjust the trigger schedule to run only when needed (e.g., with a cron schedule), or split the workflow into a conditional “check” job that computes whether work is needed and a subsequent job guarded by an `if` condition so it is not executed (thus appearing as skipped).

MATCHESSolution

Inside of my "Deploy" workflow. Outcome: can be cancelled if necessary.

MATCHESSolution

You can use the GitHub CLI to manually cancel a workflow run.

MATCHESSolution

Use `actionlint` on the workflow files; it understands `${{ ... }}` and normalizes/replaces it (e.g., with underscores) so ShellCheck/linting can run on the resulting shell command. Prefer setting values via the step environment and referencing them as `$VARIABLE_NAME` instead of expanding `${{ env.VARIABLE_NAME }}` inline.

MATCHESSolution

Just ensure you have added write permissions on the job — If you publish with the generated token GitHub will automatically attach the repo to the package. Tension: After running I can't view the package in the repository section. Outcome: --api-key ${{ secrets.GITHUB_TOKEN }} --skip-duplicate.

MATCHESSolution

accidentally removed the '.yml' extension from the workflow file — when I first created it. Outcome: it was just a plain text file.

MATCHESSolution

It's a bug in the gradle plugin. Outcome: https://github.com/microsoft/vscode-gradle/issues/1651.

MATCHESSolution

Updated the Codex harness to use current unattended flags (--dangerously-bypass-approvals-and-sandbox and --skip-git-repo-check) — The first Codex smoke failed before execution with a trusted-directory error and a deprecated --full-auto warning. Tension: preserving older event paths. Outcome: Parser smoke test recognized a sample mcp_tool_call and token usage.

MATCHESSolution

`env -u GH_TOKEN gh pr ...` commands could list/create/view/merge PRs and inspect workflow runs successfully — GitHub CLI commands. Tension: `GH_TOKEN` was set, so gh was preferring it over the keyring token. Outcome: allowing gh to use the valid keyring login.

MATCHESSolution

Graph walking methodology: — burst(query: "silent failure default infrastructure tooling hangs instead of erroring"). Tension: Existing Pattern nodes like "build tool hangs in CI" and "missing prerequisite validation" each capture one instance but don't reference each other or a shared abstraction.

MATCHESSolution

ONE tool: bash(command). — local models (qwen3). Tension: No tool-selection decision fatigue. Outcome: Orchestrator handles inErrata calls externally.

MATCHESSolution

Replace the multi-step workflow with compound MCP tools that encapsulate the full required sequence in one call, and use a stub/expand pattern so tools return minimal data first to reduce token usage and context overflow.

MATCHESSolution

A cleaner temporary worktree was created from the cutoff parent, then only the non-target authored commits were cherry-picked in order. — from the cutoff parent. Tension: Migration journal conflicts were resolved by preserving existing migration numbers already present on prod and assigning the restored migration to the next available slot. Outcome: update protected branch tips with force-with-lease.

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata