github-actions

I need GitHub Actions to deploy to staging and production with secrets (API keys, deploy tokens) scoped per environment, with production requiring manual approval before deploy.

I want GitHub Actions to automatically create version tags and GitHub Releases when I push to main. I use conventional commits (feat:, fix:, chore:) and want semantic version bumps based on commit typ...

My GitHub Actions workflows take 10+ minutes mainly due to installing dependencies on every run. I need to cache dependencies, understand what to cache for Python and Node.js, and handle cache invalid...

My GitHub Actions workflows queue up multiple runs when I push rapidly. I want to cancel old runs when a new commit is pushed to the same branch, while still running all checks on main.

I need my GitHub Actions workflows to access AWS services (S3, ECR, ECS) without storing long-lived AWS credentials as GitHub secrets. I want keyless authentication using OIDC.

Need to build a Docker image and push it to GitHub Container Registry (GHCR) on every push to main, with proper tagging (latest, sha, and version tags). Want to avoid rebuilding unchanged layers.

Multiple repositories have duplicate CI/CD logic (lint, test, build). Updating the workflow in each repo separately is error-prone. Need a single source of truth for shared CI steps.

CI pipeline runs tests automatically, but production deployment should require manual approval. Want automated staging deploy on merge to main, but production needs a human sign-off before deploying.

CI/CD pipeline needs secrets (API keys, deployment credentials) for different environments. Using repository-level secrets means production keys are accessible in all workflows including untrusted PRs...

Monorepo contains multiple services (api/, frontend/, mcp-server/). Every push runs all CI pipelines even when only one service changed. Need to run only the relevant pipelines based on which files ch...

CI pipeline uses matrix builds for multiple Python versions but stops all jobs when one fails. Need all matrix combinations to complete so developers see the full picture of compatibility.

As of 2026, the astral-sh/setup-uv GitHub Action stopped publishing major-only version tags (e.g., @v8) for security reasons. Using @v8 will fail to resolve. This is a departure from the common GitHub...

In a release workflow for a `schema/` submodule, the tag validator accepted `schema/X.Y.Z` but rejected `schema/vX.Y.Z`. Go module tags for subdirectory modules are typically `subdir/vX.Y.Z`, so rejec...

To simulate a GitHub release event with nektos/act, create a JSON file with the event payload (e.g. {"action":"published","release":{"tag_name":"v1.0.0"}}) and pass it via -e. For workflow_dispatch, u...

Commonly used GitHub Actions advance major versions faster than LLM training data. Acting on LLM-suggested versions without verification may reference an outdated major that misses features, performan...

Action tags are git tags and can be silently retargeted. A compromised maintainer can repoint @v4 at a malicious commit and every consumer pulls it on the next run. GitHub added an org/enterprise poli...

Unlike `pull_request`, `pull_request_target` runs against the base branch with the target repository's secrets available, while PR-author-controlled fields (title, body, branch name, head ref) feed in...

In a monorepo with multiple release workflows, a release.types:[published] trigger fires for every release regardless of tag prefix. Using push.tags with a glob filter avoids this but prevents workflo...

Running nektos/act on Apple M-series chips with --container-architecture linux/amd64 produces warnings and unreliable results. The default act images lack many tools that GitHub-hosted runners provide...