Repository navigation
Organization defaults and how to change them #42
bniladridas
announced in
Announcements
Replies: 1 comment
|
Update. This release link pointed at the Current release: v0.1.2, published 2026-03-24, at coccinella-labs/.github. Release history:
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Everything in
.github/at the repository root applies to every public repository incoccinella-labs. Repositories inherit it automatically; there is nothing to copy and nothing to enable.What is shared
Workflows
ci.yml.[test], thenruff check,ruff format --checkandrun_tests.py. Uploads coverage to Codecov withfail_ci_if_error: false.ci.yml(codeql job)ci.yml(gui-smoke job)python3-tkandxvfb, then runsscripts/gui-e2e.pyunder a virtual display.cla.ymlrepository_owner == 'coccinella-labs'. Sparse-checks outsigned.jsonand uses the privatebniladridas/cla-bot.auto-close-prs.ymllock-merged-prs.ymlgh pr lockand deletes the branch.update-org-activity.yml*/30 * * * *, plus push and manual dispatchprofile/README.md. Uses a concurrency group withcancel-in-progressso overlapping runs do not collide.Community health files
.github/CODEOWNERS-* @bniladridas.github/ISSUE_TEMPLATE/bug_report.md.github/ISSUE_TEMPLATE/feature_request.md.github/PULL_REQUEST_TEMPLATE.md.github/dependabot.ymlRepository settings
.github/settings.ymldefines branch protection formain: required status checkstestandcodeql, one approving review, admins included, force pushes and deletions disallowed.Changing a default
Warning
A change here lands on every public repository in the organization on its
next workflow run. Adding or tightening a required status check can block
merges across the org until every repository reports it.
mainin this repository.python check_all.pylocally. It runsruff check .,ruff format --check .,bandit -r main.pyandrun_tests.py.Tip
Test a default against a scratch repository before merging. Create a
throwaway public repo and verify the inherited workflow behaves as intended.
Where this fits
The same repository also carries the
git-guipackage. That part is a normal Python project and is versioned separately. See what lives in this repository.All reactions