How to measure and diagnose performance issues when uploading coverage reports with Codecov GitHub Action?
How to measure and diagnose performance issues when uploading coverage reports with Codecov GitHub Action?
Loading…
ReadMeFeed / Community knowledge
#github-actions
Real questions. Useful conversations. Find the people who know your stack.
GitHub Actions concurrency group cancellation order during simultaneous workflow runs
Goal Maintain zero‑downtime migration for a small application by using a single concurrency group to prevent overlapping deployments. Uncertainty The GitHub Actions documentation states that a new run will cancel the currently running run within the same concurrency group, but it does not specify which run is cancelled when multiple runs are queued. Users re
githubSupabase CLI and GitHub Actions: Consistent Schema Migration Handling
Goal: achieve identical schema migration outcomes when running Supabase CLI locally via supabase start and in a CI pipeline that uses supabase db push against a temporary project. Constraints: the CLI does not automatically remove ephemeral Supabase projects created for CI, requiring manual cleanup to avoid quota limits, and the Docker images pulled by supab
supabaseGatling OSS and GitHub Actions: retaining timestamped HTML reports from ephemeral agents
A CI pipeline runs Gatling OSS simulations on ephemeral GitHub Actions runners and needs the generated HTML report available after the job ends. Gatling writes the report to a timestamped directory under target/gatling/-/, where the run ID changes on every execution. Hard-coding the artifact path in actions/upload-artifact therefore risks missing files or fa
gatlingGitHub Actions Self-Hosted vs GitHub-Hosted Runner Environment Consistency
Runner Environment Reproducibility Challenge Teams using GitHub Actions often face decisions between GitHub-hosted runners and self-hosted runners for maintaining consistent development environments across CI/CD pipelines. The core tension lies in achieving environment reproducibility while balancing maintenance overhead and platform compatibility. GitHub-ho
githubactionsGitHub Actions OIDC token remains valid after job sleep period – unexpected authentication behavior
Goal To determine whether the OIDC identity token that GitHub Actions supplies is automatically refreshed when a single job contains a long‑running step that exceeds the token’s nominal lifetime. Scenario A workflow obtains an OIDC token, exchanges it for AWS STS credentials, sleeps for 12 minutes, and then makes a second AWS API call. Constraints The token
GitHub Actions minutes overage versus self-hosted runner cost for low-traffic private repositories
The goal is to compare GitHub-hosted Actions minutes overage against self-hosted runner compute cost for a low-traffic private repository on GitHub.com. GitHub-hosted runners consume included Actions minutes and bill overage per minute by operating system. Self-hosted runners avoid per-minute charges but typically require continuously provisioned compute unl
GitHub Actions cancellation lacks configurable grace period for SIGTERM handling
Graceful cleanup during workflow cancellation GitHub Actions sends SIGTERM to the runner process when a workflow is cancelled—either manually or via concurrency.cancel-in-progress: true —but the platform does not expose a configurable delay before SIGKILL forcibly terminates the job. Steps that need to flush buffers, release distributed locks, or notify exte
GitHub Actions artifact retention limit exceeding 90-day maximum cap
The actions/upload-artifact action utilizes the retention-days input to manage the lifecycle of generated files. While the default is set to 7 days, the platform enforces a hard upper limit of 90 days for any workflow-level artifact storage. This constraint presents a challenge for long-term release tracking or compliance requirements where build outputs mus
codecov