ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Goal To revert repository changes made by a workflow that ran after a schema change, using only GitHub Actions and the GitHub REST API. Current Constraints The REST API can trigger a workflow via workflow_dispatch and cancel a running workflow, but canceling does not undo commits or other side‑effects that have already occurred. Manual rollback requires a cu
Secret Availability Across Runner Types The goal is to guarantee that a secret defined in the repository is accessible as an environment variable in every job step, irrespective of whether the workflow runs on a self-hosted or GitHub-hosted runner. Constraints include the requirement to explicitly map secrets to env vars in the workflow YAML, the potential f
Goal Determine whether a deployment that fails a step automatically marks the required status check as failed, and evaluate the trade‑off between using the Actions UI logs and creating an artifact for debugging. Constraints GitHub Actions retains job logs for 90 days (public or private repositories), but the UI offers no cross‑job search and limits visibilit
Managing database schema changes within a CI/CD pipeline requires a strategy for reverting changes when a deployment fails. GitHub Actions provides environment protection rules that allow for manual approvals and gated deployments, creating a controlled window to abort a process before it reaches production. However, GitHub Actions does not natively track or
A repository configures GitHub Actions jobs with runs-on: ubuntu-latest . Builds that previously succeeded may fail on an unchanged commit when GitHub updates the hosted runner image behind the latest alias. The goal is to diagnose whether runner image drift, rather than a repository or workflow regression, explains the failure. ubuntu-latest is not a fixed
Integration boundary The goal is to define the supported trust boundary for a GitHub Actions self-hosted runner that must reach GitHub.com while a workflow step also connects to an internal service using a privately issued TLS certificate. The runner’s control traffic and job-step traffic may share the host or container trust store, but the documented behavi
github
githubactions