Rename workflows for better understanding

[rgsl888prabhu]

Description

Workflows had minimal names and would miss there actual significance while looking up in actions. So these have been renamed to provide more details.

Checklist

• I am familiar with the Contributing Guidelines.
• Testing
  • New or existing tests cover these changes
  • Added tests
  • Created an issue to follow-up
  • NA
• Documentation
  • The documentation is up to date with these changes
  • Added new documentation
  • NA

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 627bb141-44f8-4e87-a439-ca824428749c

📥 Commits

Reviewing files that changed from the base of the PR and between e394ae4 and 5896638.

📒 Files selected for processing (3)

• .github/workflows/inactivity_reminder.yaml
• .github/workflows/self_hosted_service_test.yaml
• .github/workflows/test_images.yaml

✅ Files skipped from review due to trivial changes (3)

• .github/workflows/inactivity_reminder.yaml
• .github/workflows/test_images.yaml
• .github/workflows/self_hosted_service_test.yaml

---

📝 Walkthrough

Walkthrough

Updated display name fields in seven GitHub Actions workflow files to use more descriptive titles; one workflow also updated an SPDX year and one job display name was clarified. No workflow triggers, jobs, steps, inputs/outputs, or execution logic were modified.

Changes

Cohort / File(s)	Summary
Workflow display name edits \.github/workflows/build.yaml, \.github/workflows/pr.yaml, \.github/workflows/test.yaml, \.github/workflows/test_images.yaml	Updated top-level name: values: build → Branch, release, tag, and nightly build, pr → Pull Requests, test → Branch, release, tag, and nightly tests, Test images → Test cuOpt container images. No functional changes.
Image workflow and job display name \.github/workflows/build_test_publish_images.yaml	Renamed workflow name to “Build, test, and publish cuOpt container images” and changed test-images job display name to “Test cuOpt container images”. No logic changes.
Inactivity/stale reminders \.github/workflows/inactivity_reminder.yaml	Changed workflow name from “Inactivity Reminder with Different Times” to “Stale issue and PR reminders”. No other edits.
Self-hosted service workflow metadata \.github/workflows/self_hosted_service_test.yaml	Renamed workflow name to “Self-hosted service tests” and updated SPDX header year (2023-2025 → 2023-2026). No behavior changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main changeset: all modifications across six workflow files are exclusively workflow display name updates.
Description check	✅ Passed	The description clearly explains the rationale for the changes: minimal workflow names were renamed to provide more details for better visibility in GitHub Actions.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[jameslamb]

Can you please leave the names of build.yaml, pr.yaml, and test.yaml untouched?

These are RAPIDS-wide conventions and those conventions are useful for reducing the cognitive burden when switching between repos.

No opinion on the other changes.

[rgsl888prabhu]

Can you please leave the names of build.yaml, pr.yaml, and test.yaml untouched?

These are RAPIDS-wide conventions and those conventions are useful for reducing the cognitive burden when switching between repos.

No opinion on the other changes.

Is there an option where I can add additional details to this so it is also available in actions ?

[jameslamb]

Is there an option where I can add additional details to this so it is also available in actions ?

Depends on what you mean by "available in actions".

Here's what I'm aware of:

• you can add a code comment in the workflow files so anyone touching them can see what their purpose is (does not affect the GitHub UI)
• you can set the name property on individual jobs within the workflow (affects the GitHub UI)

Besides sticking to our conventions, please do look at how this shows up in the GitHub UI for PRs.

Pull Requests (13 characters) is longer than pr (2 characters), and so more details about individual jobs are getting pushed into ... that you'd have to click into to see.