[scanner] fix: pin kubestellar/infra reusable workflows to immutable commit SHA

[Copilot]

📌 Fixes

Issue linking is handled automatically by the system.

---

📝 Summary of Changes

• This PR removes mutable reusable-workflow references to kubestellar/infra@main in docs CI workflows and pins them to immutable commit 9a15d65135864435badfb9293251e8701b562899.
• It also tightens workflow token scope in copilot-dco.yml with explicit top-level permissions.

---

Changes Made

• Updated reusable workflow refs in:
  • .github/workflows/add-help-wanted.yml
  • .github/workflows/ai-fix.yml
  • .github/workflows/assignment-helper.yml
  • .github/workflows/copilot-automation.yml
  • .github/workflows/copilot-dco.yml
  • .github/workflows/feedback.yml
  • .github/workflows/greetings.yml
  • .github/workflows/label-helper.yml
  • .github/workflows/scorecard.yml
• Fixed mutable ref usage by replacing @main with @9a15d65135864435badfb9293251e8701b562899 # main
• Fixed workflow permission hardening gap by adding:

  permissions:
    contents: read

  to .github/workflows/copilot-dco.yml
• Added tests for workflow YAML changes (not applicable)

---

Checklist

Please ensure the following before submitting your PR:

• I have reviewed the project's contribution guidelines.
• I have performed a self-review of my changes.
• I have written unit tests for the changes (if applicable).
• I have updated the documentation (if applicable).
• I have tested the changes locally and ensured they work as expected.
• All CI checks are passing.

Security Considerations

If this PR modifies any security-sensitive files, confirm:

• Dockerfiles — verified base images, avoided running as root
• Kubernetes manifests — checked RBAC permissions and secrets handling
• CI/CD workflows — inspected for command injection or credential exposure
• Dependencies — validated new packages, checked for known vulnerabilities
• Security configs — changes align with project security policies

Leave unchecked if not applicable. See CONTRIBUTING.md for details.

---

Screenshots or Logs (if applicable)

---

👀 Reviewer Notes

• Scope is intentionally narrow: only workflow ref pinning plus one explicit-permissions hardening update in copilot-dco.yml.

[kubestellar-prow]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[kubestellar-prow]

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.

📝 Please follow instructions in the contributing guide to update your commits with the DCO

Full details of the Developer Certificate of Origin can be found at developercertificate.org.

The list of commits missing DCO signoff:

• 8e44926 Initial plan

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

[netlify]

❌ Deploy Preview for kubestellar-docs failed. Why did it fail? →

Name	Link
🔨 Latest commit	8e44926
🔍 Latest deploy log	https://app.netlify.com/projects/kubestellar-docs/deploys/6a33708d6207740008d1849d

[kubestellar-prow]

Hi @Copilot. Thanks for your PR.

I'm waiting for a kubestellar member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.