refactor: reorganize GitHub workflows with consistent naming convention #5891
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Implement systematic naming convention using category prefixes - Group workflows logically: ci-, pr-, release-, types-, i18n- - Rename all 22 workflows for better organization and discoverability - Update workflow cross-references and display names - Add comprehensive README.md with naming guidelines and best practices Key changes: - CI workflows: ci-tests-e2e, ci-tests-unit, ci-tests-storybook, etc. - PR automation: pr-backport, pr-claude-review, pr-playwright-snapshots - Release management: release-version-bump, release-npm-types, etc. - Type generation: types-registry-api, types-manager-api, etc. - Internationalization: i18n-update-core, i18n-update-nodes, etc. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
dosubot
bot
added
the
size:L
|
This might break a lot of other things like branch protection rules |
These probably aren't the names I would have gone with, but this was my idea to make the actions a little more organized and make it easier to find related workflows. The branch protection rules would almost definitely need to be updated, GitHub isn't great about noticing changes like that. |
|
Should be fine as long as we update BP when merging. I think there's some other things like documentation, claude commands, and the PyPi and NPM auth stuff. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR implements a systematic naming convention for all GitHub workflows to improve organization and discoverability. All 22 workflows have been renamed and grouped by logical categories with consistent prefixes.
Changes
Naming Convention
ci-*: Continuous Integration workflows (testing, linting, validation)pr-*: PR-specific automation triggered by labelsrelease-*: Release management workflowstypes-*: TypeScript type generation workflowsi18n-*: Internationalization workflowsKey Renames
tests-ci.yaml→ci-tests-e2e.yamlvitest-tests.yaml→ci-tests-unit.yamlstorybook-and-chromatic-ci.yaml→ci-tests-storybook.yamlauto-backport.yaml→pr-backport.yamlclaude-pr-review.yml→pr-claude-review.yamlversion-bump.yaml→release-version-bump.yamlpublish-frontend-types.yaml→release-npm-types.yamlcreate-dev-pypi-package.yaml→release-pypi-dev.yamlTest Workflow Improvements
ci-tests-*patternci-tests-e2e-forks.yaml,ci-tests-storybook-forks.yamlDocumentation
.github/workflows/README.mdBenefits
Test Plan
🤖 Generated with Claude Code
┆Issue is synchronized with this Notion page by Unito