ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #github
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
Goal: Retrieve large sets of GitHub issues efficiently while staying within rate‑limit and payload constraints. Currently the REST API uses page‑based pagination with a per_page ceiling of 100 items, but internal discussions suggest a move toward cursor‑based pagination for more stable navigation. It is unclear whether the page parameter will remain supporte
Read the Docs integrates with GitHub via webhooks to automate documentation builds upon commits to tracked branches. While the platform allows maintainers to enable build failure notifications via email, the current configuration options apply broadly to the project's build status. In environments with multiple tracked versions—such as a stable production br
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
Goal: enforce a maximum wait time and allow cancellation for long‑running GitHub API operations such as creating a deployment or merging a pull request. Constraint: a synchronous request blocks until the server finishes or the client’s timeout expires, yielding no progress information and a hard 504‑like failure if the limit is hit; using the Prefer: respond
Operating system: Linux git version: 2.26.2 Git repo provider of my repo: gitlab Repo provider of the failing submodules: Github .gitmodules [submodule "libraries/stb"] path = libraries/stb url = https://github.com/nothings/stb.git branch = master [submodule "libraries/harfbuzz"] path = libraries/harfbuzz url = https://github.com/harfbuzz/harfbuzz.git branch
Migrating a Small Application from GitHub to Forgejo The goal is to move the repository while keeping the application online, preserving webhooks, CI pipelines, and branch protection rules. Constraints include the lack of an automated bulk webhook export, the need to manually recreate branch protection settings, and the temporary database lock required for a
Integration Challenge: State Persistence in Codeac GitHub Ephemeral Environments The Codeac platform uses GitHub repositories to provision ephemeral development environments defined by codeac.yaml . When an environment is destroyed and recreated from a specific branch, the system restores runtime and dependencies but does not automatically address stateful d
I have a private repo with a GitHub Action that pushes the code to an AWS S3 bucket when there's a new push to the master branch. I need a pair of access keys to be able to push the contents and I'm storing them as GitHub Secrets and referencing them as environment variables in the build script. Now I would like to make this repo public in the near future, a
towergit
readthedocs
git
gitlab
forgejo
codeac