ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
DevOps & observability · #githubactions
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
Objective Keep long-lived cloud access keys stored as GitHub Actions secrets from remaining valid after expiration or rotation, without relying on manual cleanup. This applies to GitHub Actions on GitHub.com and GitHub Enterprise Server where Actions is enabled. GitHub Actions does not display or enforce an expiration date for encrypted repository, environme
Implementing least-privilege authentication in GitHub Actions via OpenID Connect (OIDC) allows workflows to exchange short-lived tokens for cloud IAM roles. This removes the need for long-lived secrets but introduces complexity in trust relationship configuration. In a multi-tenant organization with numerous repositories, a broad trust policy based only on t
Goal Determine whether the built-in timing information shown for each workflow step in the GitHub Actions UI on GitHub.com isolates artifact upload and download duration, or rolls that time into the surrounding step, before deciding where to focus optimization. Constraints and uncertainty Step timing in the run UI reflects wall-clock time on the runner. Arti
Goal Select a cache key strategy for GitHub Actions dependency caching that balances artifact freshness against cache hit rates in a repository with frequent transitive dependency updates. Constraints and uncertainty The actions/cache action uses an immutable primary key (typically a hash of lockfiles) and optional restore-keys for fallback. Stale restores o
The same project needs to behave consistently on developer machines, in CI and after deployment. Which versions, dependencies and configuration should be recorded?
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
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?