standardize: naming conventions #1

Merged
mik-tf merged 2 commits from development_hero_zero_standardize into main 2026-02-12 00:55:44 +00:00
Owner

Changes

Package Renames

  • Package: hero_dev_toolshero_dev
  • Library: hero_dev_toolshero_dev
  • Binary: hero-dev-toolshero_dev
  • buildenv.sh: PROJECT_NAME and BINARIES updated
  • Source: use hero_dev_tools::use hero_dev:: (4 imports in main.rs)

Build passes.

## Changes ### Package Renames - Package: `hero_dev_tools` → `hero_dev` - Library: `hero_dev_tools` → `hero_dev` - Binary: `hero-dev-tools` → `hero_dev` - `buildenv.sh`: PROJECT_NAME and BINARIES updated - Source: `use hero_dev_tools::` → `use hero_dev::` (4 imports in main.rs) **Build passes.**
standardize: rename package/binary to match repo name hero_dev
Some checks are pending
Build and Test / build (pull_request) Waiting to run
Build and Test / build (push) Successful in 21s
439a1319dc
- Cargo.toml: package hero_dev_tools → hero_dev
- Cargo.toml: lib name hero_dev_tools → hero_dev
- Cargo.toml: binary hero-dev-tools → hero_dev
- src/main.rs: use hero_dev_tools:: → use hero_dev::
- buildenv.sh: PROJECT_NAME → hero_dev, BINARIES → hero_dev
- Makefile: all binary references updated

Per naming_convention skill: package and binary must match repo name in snake_case.
mik-tf changed title from Standardize: naming convention, ports, Makefile compliance to standardize: naming conventions 2026-02-12 00:01:52 +00:00
ci: restrict test triggers to PRs and push to development/main
All checks were successful
Build and Test / build (pull_request) Successful in 42s
821fc09dd7
Stop triggering test/build workflows on every push to every branch.
Tests now run only on:
- push to development or main (post-merge validation)
- pull_request targeting development or main (pre-merge check)
- manual workflow_dispatch

Per forge_ci skill: Standard Workflow Triggers convention.
mik-tf merged commit ba8f55a3a4 into main 2026-02-12 00:55:44 +00:00
mik-tf deleted branch development_hero_zero_standardize 2026-02-12 00:55:45 +00:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_dev!1
No description provided.