feat: disable deployments on workflows

[jackhodgkiss]

When using environments in workflows they get treated as a deployment which in unnecessary and leads to a trail of events associated with a given PR.

See: https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/control-deployments#using-environments-without-deployments

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: stackhpc/stackhpc-kayobe-config/.coderabbit.yaml
• Review profile: CHILL
• Plan: Advanced
• Run ID: 422e6341-0c47-467a-a2e2-2d6bc7783c48

📥 Commits

Reviewing files that changed from the base of the PR and between 26d7d4b and 8b894c3.

📒 Files selected for processing: 6

• .github/workflows/amphora-image-build.yml
• .github/workflows/ipa-image-build.yml
• .github/workflows/overcloud-host-image-build.yml
• .github/workflows/package-build-ofed.yml
• .github/workflows/runner-selector.yml
• .github/workflows/stackhpc-all-in-one.yml

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

📝 Walkthrough

Six GitHub Actions jobs now configure their environments with a mapping. Each mapping retains the existing environment name and sets deployment to false.

Changes: Workflow environment configuration

Layer / File(s)	Summary
Job environment mappings .github/workflows/runner-selector.yml, .github/workflows/amphora-image-build.yml, .github/workflows/ipa-image-build.yml, .github/workflows/overcloud-host-image-build.yml, .github/workflows/package-build-ofed.yml, .github/workflows/stackhpc-all-in-one.yml	The six jobs replace scalar environment names with mappings that set the same name and deployment: false.

Priority: ⬇️ Low

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

Merge Risk: ⚪ Minimal · up to 8b894

The workflows retain their environments while suppressing deployment records. No concrete workflow failure is established, so no actionable merge blocker is identified.

Pre-merge checks: 3

Check name	Status	Explanation
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (6 skipped: 6 unsupported.)

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

[Alex-Welsh]

I'll be very glad to never see that deployment spam again!