Skip to content

Update to template-python v0.1.1 - #21

Merged
MrKevinWeiss merged 2 commits into
masterfrom
pr/copier-update-v0.1.1
Sep 29, 2026
Merged

MrKevinWeiss merged 2 commits into
masterfrom
pr/copier-update-v0.1.1

Conversation

@MrKevinWeiss

Copy link
Copy Markdown
Collaborator

No description provided.

Also drops two files the template stopped generating after the tag:

- `.github/agents/pr-review.agent.md`
- `.github/copilot-instructions.md`

Copilot is used for PR review on GitHub, not locally, and the copilot file held
no content of its own — only a pointer, and a broken one: from inside `.github/`
the link resolved to `.github/.github/instructions/...`. The dangling "## Agents"
section that pointed at the deleted agent file is removed from
`.github/instructions/lobaro-template.instructions.md` with it.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
@MrKevinWeiss
MrKevinWeiss force-pushed the pr/copier-update-v0.1.1 branch from 61818b9 to cb19545 Compare September 29, 2026 10:10
python-lob-helpers is the only public repository in the set; every other repo the
template feeds is private. GitHub's self-hosted runner groups do not allow public
repositories by default, so the jobs the template generates simply queue forever —
two runs sat at `queued` with labels ["self-hosted","uv"] and an empty
runner_group_name for ~40 minutes while seven private repos with identical labels
started in seconds.

Enabling public repos on the runner group would be the wrong fix: a pull request
from any fork would then run arbitrary code on our infrastructure. GitHub-hosted
runners are the right answer for a public repo.

The template gets a `self_hosted_runners` answer so this stops being a local edit;
until that lands and is tagged, this file diverges from the template by these four
lines.

Co-Authored-By: Claude Opus 5 (1M context) <[email protected]>
@MrKevinWeiss
MrKevinWeiss merged commit e54f770 into master Sep 29, 2026
6 checks passed
@MrKevinWeiss
MrKevinWeiss deleted the pr/copier-update-v0.1.1 branch September 29, 2026 10:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant