fix: update GitHub workflow names (#1284)

[parvninama]

This PR updates the workflow names in .github/workflows/bot-workflows.yml to match the expected naming conventions.

• Corrects workflow identifiers so the automation bots can detect and run the workflows properly.
  -No functional code changes are included; this is purely a maintenance/documentation update.

Closes (#1284)

[github-actions]

Hi, this is MergeConflictBot.
Your pull request cannot be merged because it contains merge conflicts.

Please resolve these conflicts locally and push the changes.

To assist you, please read:

• Resolving Merge Conflicts
• Rebasing Guide

Thank you for contributing!

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

@@           Coverage Diff           @@
##             main    #1298   +/-   ##
=======================================
  Coverage   91.80%   91.80%           
=======================================
  Files         139      139           
  Lines        8484     8484           
=======================================
  Hits         7789     7789           
  Misses        695      695           

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[coderabbitai]

📝 Walkthrough

Walkthrough

GitHub Actions workflow trigger name updated from "Hiero Solo Integration Tests" to "Hiero Solo Integration & Unit Tests" in the bot workflow configuration. Corresponding changelog entry added to document this change.

Changes

Cohort / File(s)	Summary
GitHub Actions Configuration \.github/workflows/bot-workflows\.yml	Updated on.workflow_run.workflows trigger to reference "Hiero Solo Integration & Unit Tests" instead of "Hiero Solo Integration Tests"
Documentation CHANGELOG\.md	Added unreleased changelog entry documenting the workflow name update (#1284)

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Pre-merge checks

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main change: updating GitHub workflow names. It is concise, clear, and directly related to the changeset modifications in .github/workflows/bot-workflows.yml.
Description check	✅ Passed	The description is directly related to the changeset, explaining that workflow names were updated to match naming conventions and that this is a maintenance update with no functional code changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 85b7059 and e0c5272.

📒 Files selected for processing (2)

• .github/workflows/bot-workflows.yml
• CHANGELOG.md

🧰 Additional context used

📓 Path-based instructions (1)

.github/workflows/**/*

⚙️ CodeRabbit configuration file

.github/workflows/**/*: Review workflows as security-sensitive infrastructure.

A good workflow is small, focused, and boring.
If a workflow is clever, generic, or overly flexible, it is a risk.

---

PRIORITY 0 — ABSOLUTE REQUIREMENTS

• All third-party actions MUST be pinned to full commit SHAs, similar to other workflows.
• permissions: MUST be explicitly declared and minimally scoped.
• Workflows MUST behave safely when executed from forks.
• YAML MUST orchestrate steps, not implement business logic.
• Any workflow that mutates GitHub state MUST support dry-run mode.
• Dry-run behavior must be explicit and visible in logs.
• Workflows MUST NOT modify repository source code outside .github/.

---

PRIORITY 1 — SCOPE, FOCUS & RESTRAINT

• The title of each workflow must be relevant, match similar naming schemes, and match its script filename.
• Each workflow MUST have a single, clearly defined objective and SHOULD document this in a top-level comment.
• Flag workflows that:
  • Attempt to be generic “frameworks”
  • Include speculative or future-facing logic
  • Perform actions unrelated to the stated goal
• Over-abstraction and excess flexibility are maintenance risks.

---

PRIORITY 2 — INPUT HARDENING

• Treat ALL GitHub event data as potentially hostile input, including:
  • issue titles, bodies, and comments
  • labels, usernames, branch names
• Free-form user input MUST NOT be passed directly into:
  • shell commands
  • gh CLI arguments
  • Node.js exec / spawn calls
• Require strict allowlists or exact string matches.
• Flag any use of:
  • eval or bash -c
  • backticks or $(...) with user-controlled input

------------------...

Files:

• .github/workflows/bot-workflows.yml

🪛 LanguageTool

CHANGELOG.md

[uncategorized] ~81-~81: The official name of this software platform is spelled with a capital “H”.
Context: ...anged -Update GitHub workflow names in .github/workflows/bot-workflows.yml to match c...

(GITHUB)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (7)

• GitHub Check: build-and-test (3.10)
• GitHub Check: build-and-test (3.11)
• GitHub Check: build-and-test (3.13)
• GitHub Check: build-and-test (3.12)
• GitHub Check: run-examples
• GitHub Check: Codacy Static Code Analysis
• GitHub Check: StepSecurity Harden-Runner

🔇 Additional comments (1)

.github/workflows/bot-workflows.yml (1)

8-8: The workflow trigger reference is correct.

The workflow "Hiero Solo Integration & Unit Tests" exists in .github/workflows/pr-check-test.yml and the trigger reference is properly configured.

[exploreriii]

Thank you again @parvninama