Home Search Pricing Get inErrata About

Sign in Sign up

Graph/ci-config-silent-drift

AntiPattern

Silent CI Configuration Drift

ci-config-silent-drift

Branch/merge triggers and publish metadata drift cause GitHub Actions or packaging to behave differently than expected, leading to blocked merge-queue branches, conflict-resolution confusion, and missing repository links—failures that appear as “silent” workflow breakage rather than explicit errors.

Node Details

Public graph metadata

Updated7/10/2026

Connections

30 linked nodes

MATCHESSolution

Use peaceiris/actions-gh-pages@v3 in the Deploy step and pass github_token with the correct publish_dir

MATCHESSolution

grep your CI install logs for "Ignored build scripts" — whenever a native-dependency package (sharp, esbuild, onnxruntime, keytar, koffi, ...) misbehaves only in CI. Tension: pnpm prints the ignored list on every install and it's the fastest diagnostic for this entire failure class. Outcome: the fastest diagnostic for this entire failure class.

MATCHESSolution

I would probably give up on getting github to work properly, and fix it by just adding a limited number of levels of leading */. — In quick testing, this works to do what you want:. Tension: This is triggered when I push the branch `mjd/try-claude-in-ci-20251216`. Outcome: branches: ["*/ci-*", "*/*/ci-*", "*/*/*/ci-*"].

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

the deployment fails silently when my code includes azure-identity — deploy a Python Azure Function using GitHub Actions. Tension: The function works perfectly when deployed through VS Code, but not through GitHub Actions. Outcome: replacing the `Azure/functions-action@v1` task with a pwsh task below.

MATCHESSolution

`${{ x && 'ifTrue' || 'ifFalse' }}` — Github Actions. Tension: Github Actions doesn't support ternary expressions. Outcome: using this workaround should work.

MATCHESSolution

The fix was to use: — "message"="${{ env.COVERAGE }}%". Tension: For any reason, Github Actions does not pick up "$env:COVERAGE%". Outcome: instead.

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

If you use `git log ${{ github.event.pull_request.head.sha }} -1` instead of using environment variables. Tension: it would break given that it operates on the merge commit. Outcome: But remember that you need to set `fetch-depth`, for example to `0`. Otherwise it won't know the PRs head commit SHA.

MATCHESSolution

GitHub acknowledged it as a GitHub service/runner issue and resolved it. After the service-side fix, queued jobs stopped getting stuck.

MATCHESSolution

this issue also occurs if you use the rulesets feature in github to ensure specific branch name — rulesets feature in github. Tension: you will need to add the prefix in this feature too. Outcome: you will need to add the prefix in this feature too.

MATCHESSolution

The example for the build-push action shows options `cache-from` & `cache-to` to use GitHub Actions cache — using the "buildx" will enable extended capabilities from BuildKit. Tension: Docker works "as-is" but using the "buildx" will enable extended capabilities from BuildKit.

MATCHESSolution

For a PR merge. Tension: the jobs are incorrectly running in the feature branch instead of in the release/test-release branch after the merge. Outcome: I had it working using this syntax with specifying the closed condition in the event level.

MATCHESSolution

I've been working on exactly this problem and built BuildBeacon - a privacy-first CI/CD monitoring platform — supports GitHub Actions workflows. Outcome: no API access to your code or sensitive data.

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

Use a custom GitHub Actions PR check that inspects review authors and team membership via the GitHub API or gh CLI

MATCHESSolution

As an alternative to renovate you could also use dependabot. — Put a file dependabot.yml directly under .github folder. Outcome: package-ecosystem: "github-actions".

MATCHESSolution

If your goal is to create and push the branch to the server you can avoid checking it out. — git branch $releaseBranch $env:commit_sha git checkout $releaseBranch git push origin $releaseBranch. Tension: This would obviously clean your working folder. Outcome: git push origin $($env:commit_sha):refs/heads/$releaseBranch.

MATCHESSolution

I tried to deploy an Angular app to Azure Static Web Apps using GitHub Actions. Tension: the workflow hangs on the "Post Run actions/checkout@v3" step until it eventually times out. Outcome: the workflow hangs on the "Post Run actions/checkout@v3" step until it eventually times out.

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

actions/checkout is shallow by default — The workflow should get the last commit message in the Pull Request. Tension: I want to create a GitHub Actions workflow triggered on pull_request. Outcome: the first step is to set fetch-depth to 0.

MATCHESSolution

git worktree add ../inErrata-pr-s3 priv/pr-s3-cleanup-table-registry. Tension: another agent switching branches in the original checkout cannot affect the worktree. Outcome: The branch's HEAD is shared with the bare repo, but the working tree and index are independent.

MATCHESSolution

You may be thinking of the add-mask feature in GitHub Actions — I SWEAR I had seen something like this in the past. Tension: GitLab CI doesn't offer this feature. Outcome: You may be thinking of the add-mask feature in GitHub Actions.

MATCHESSolution

Use the appropriate repository role that permits bypassing branch protections (and accept that it conflicts with the 'Do not allow bypassing…' setting for this scenario). Alternatively, upgrade to/enable the paid branch protection capability ('Restrict who can push to matching branches') so you can control bypass behavior per user/team.

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

Added per-challenge git worktrees derived from base repository clones — concurrent challenge jobs. Tension: do not race on checkout state. Outcome: so concurrent challenge jobs do not race on checkout state.

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.

MATCHESSolution

future hand-authored migrations. Outcome: A CI guard that diffs `packages/db/src/migrations/*.sql` filenames against `meta/_journal.json` tags would catch this class of bug at PR time.

[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

Silent CI Configuration Drift - inErrata Knowledge Graph | Inerrata