ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
In github actions I'm running an action that is trying to use github to GCP federated id: # see https://github.com/marketplace/actions/authenticate-to-google-cloud#setup - id: 'auth' name: 'Authenticate to Google Cloud' uses: 'google-github-actions/auth@v0' with: workload_identity_provider: 'projects/1234/locations/global/workloadIdentityPools/my-github-pool
GitHub Actions provides a caching mechanism to accelerate workflows by storing dependencies and build artifacts. According to the documentation, there is a 5 GB limit per cache for a single repository. When a workflow attempts to save a cache that exceeds this 5 GB threshold, the specific failure mode remains unclear. It is uncertain whether the system perfo
Integration Gap When integrating GitHub Actions workflow retries with the REST API's idempotency-key mechanism, the platform does not automatically generate or propagate Idempotency-Key headers across retry attempts. This leaves a gap where transient failures (rate limits, network errors) trigger retries that the API treats as new requests, potentially creat
Diagnostic goal A workflow needs a defined cleanup contract when a GitHub Actions job is cancelled or reaches jobs.<job_id>.timeout-minutes . The documented jobs.<job_id>.cancel-timeout-minutes setting controls the cancellation grace period, but it does not by itself establish that step processes receive a particular termination signal or that cl
I was wondering how I can set the system path variables in the GitHub actions workflow. export "$PATH:$ANYTHING/SOMETHING:$AA/BB/bin"
Goal: Ensure that a workflow_dispatch trigger only accepts predefined values for a choice‑typed input, regardless of whether the workflow is started from the GitHub UI or the REST API. Current behavior: GitHub validates that the input exists and matches the declared type (string) but does not verify that the supplied value is one of the enumerated options de
I am creating a workflow in GitHub which creates and uses a docker image. Therefore I have started my workflow file with a global environment variable for this docker image which is visible for all the jobs in my workflow: name: continuous integration on: push: branches: - '**' env: IMAGE: docker.pkg.github.com/${{ github.repository }}/jactor-persistence:${{
Context In GitHub Actions, repository secrets are omitted when a workflow runs on a pull request originating from a forked repository. Locally, developers can set environment variables or use local secret files, making the same workflow appear to succeed. In production, the missing secrets cause the job to fail. Unresolved Decision The core issue is whether
Context A private repository with low traffic currently uses GitHub Actions. The free tier provides 2,000 minutes per month. Workflows occasionally exceed this limit, incurring per‑minute charges for GitHub‑hosted runners. An alternative is to deploy a self‑hosted runner , which avoids GitHub‑side billing but introduces hardware, power, bandwidth, and mainte
answered · 08 Nov 2021, 07:55 UTC
github
docker
git