refactor: unify rust-native ares template naming and documentation#218
Merged
refactor: unify rust-native ares template naming and documentation#218
Conversation
…nces **Changed:** - Standardized all "ares-rust-*" template directories and files to use the "ares-*" naming convention for consistency - Updated all README.md and documentation references from "ares-rust-*" to "ares-*" to match the new naming scheme - Modified template metadata and configuration files to reflect the unified template names - Adjusted CI build workflow to remove special handling for ares-rust-worker and ares-rust-worker-gpu in GPU dependency chains - Renamed GPU matrix variables and documentation to match new ares-python-* and ares-* naming conventions - Updated infrastructure and template usage documentation to reflect the new directory and image names - Ensured all build, deployment, and validation instructions use the unified naming scheme for clarity **Removed:** - Eliminated all legacy references to "ares-rust-*" and outdated GPU template names from documentation and CI workflow comments
l50
added a commit
that referenced
this pull request
Apr 18, 2026
) **Key Changes:** - Renamed all "ares-rust-*" templates and documentation to standard "ares-*" names - Updated README, build references, and documentation for consistent naming - Adjusted build and push workflow and matrix logic for new template names - Ensured all user and developer documentation reflects the unified naming **Changed:** - Template directory and file names for all Rust-native ares agents, orchestrators, and CLI are now standardized to `ares-<role>` instead of `ares-rust-<role>` - All references in documentation (README.md, infrastructure docs, template READMEs) updated to use new naming conventions for clarity and consistency - Build workflow (`.github/workflows/build-and-push-templates.yaml`) matrix logic and comments updated to match new template names and roles (e.g. `ares-cracker-agent-gpu` instead of `ares-rust-cracker-agent-gpu`) - Docker build, tag, push, and kubectl usage instructions updated across docs to reference the unified names - Template `warpgate.yaml` metadata and `name` fields updated to drop "rust" prefix and match new conventions **Removed:** - All use of the "ares-rust-*" naming pattern for templates, documentation, and workflow logic to reduce confusion and ensure one consistent naming scheme
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
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.
Key Changes:
Changed:
and CLI are now standardized to
ares-<role>instead ofares-rust-<role>updated to use new naming conventions for clarity and consistency
.github/workflows/build-and-push-templates.yaml) matrix logicand comments updated to match new template names and roles (e.g.
ares-cracker-agent-gpuinstead ofares-rust-cracker-agent-gpu)reference the unified names
warpgate.yamlmetadata andnamefields updated to drop "rust"prefix and match new conventions
Removed:
workflow logic to reduce confusion and ensure one consistent naming scheme