Skip to content

Rename the CI workflow from main to ci - #23

Merged
tomaslink merged 2 commits into
mainfrom
rename-ci-workflow
Oct 20, 2026
Merged

tomaslink merged 2 commits into
mainfrom
rename-ci-workflow

Conversation

@tomaslink

Copy link
Copy Markdown
Collaborator

Summary

The README badge shows the workflow's name:, so it read "main – passing", which looks like a branch name. Renamed the workflow to ci (.github/workflows/ci.yaml) so the badge reads "ci – passing", as in gfw-common. Repos created from the template get the same badge.

The badge still reports the default branch (GitHub's default for workflow badges), so its meaning doesn't change.

Changes

  • .github/workflows/main.yaml → ci.yaml, name: main → name: ci. Jobs unchanged.
  • README badge link and image point to ci.yaml.

Notes

  • The protect main ruleset requires checks by job name (flake8, tests - Python 3.12 on Docker, tests - Python 3.13 on ubuntu-latest), not by workflow name, so it's unaffected.
  • Repos already created from the template keep main.yaml until they adopt this.

🤖 Generated with Claude Code

The badge shows the workflow's name, so it read "main - passing", which
looks like a branch. "ci - passing" says what passed, as in gfw-common.
The badge still reports the default branch.
@tomaslink tomaslink self-assigned this Oct 20, 2026
@tomaslink
tomaslink merged commit d94a4fd into main Oct 20, 2026
3 checks passed
@tomaslink
tomaslink deleted the rename-ci-workflow branch October 20, 2026 03:35
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