ci: name publish commit-message step for readability

[MGPOCKY]

Problem

In .github/workflows/publish.yml, the get_commit_message helper run step is unnamed and longer than 300 characters. In the GitHub Actions UI that collapses into a generic label, which hurts readability when commit-message resolution fails.

Changes

Semantics are unchanged: same step id, same GITHUB_OUTPUT keys, and the same job output wiring (steps.get_commit_message.outputs.commit-message).

• Add name: Resolve commit message to id: get_commit_message

Test plan

• Confirm later jobs still use needs.pre-ci.outputs.commit-message
• Confirm the step shows the new name in the Actions UI

Summary by CodeRabbit

• Chores
  • Updated the CI workflow step label for clearer build-process reporting.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 4ac70da4-2c34-478e-aba5-6e8627d5a239

📥 Commits

Reviewing files that changed from the base of the PR and between 51e2a2c and b93eb3b.

📒 Files selected for processing (1)

• .github/workflows/publish.yml

---

📝 Walkthrough

Walkthrough

The publish workflow now displays Resolve commit message for the existing commit-message extraction step. Its step ID and execution behavior remain unchanged.

Changes

Publish workflow

Layer / File(s)	Summary
Label commit-message extraction step .github/workflows/publish.yml	The existing step now displays Resolve commit message. Its ID and execution behavior remain unchanged.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

• subquery/subql#3041: Modifies the same commit-message extraction step in .github/workflows/publish.yml.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the added name for the publish workflow commit-message step and its readability purpose.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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.}