chore(ci): authenticate GH action for ShellCheck

[zdrapela]

Description

Add GITHUB_TOKEN to avoid rate limiting while downloading ShellCheck binary

Which issue(s) does this PR fix

• Fixes #?

PR acceptance criteria

Please make sure that the following steps are complete:

• GitHub Actions are completed and successful
• Unit Tests are updated and passing
• E2E Tests are updated and passing
• Documentation is updated if necessary (requirement for new features)
• Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-4049
• quay.io/rhdh-community/rhdh:pr-4049-c6a5acd2

[openshift-ci]

@zdrapela: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-ocp-helm	c6a5acd	link	true	/test e2e-ocp-helm

Full PR test history. Your PR dashboard.

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.

[zdrapela]

/review
-i

[rhdh-qodo-merge]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🔒 No security concerns identified

⚡ Recommended focus areas for review Token usage Validate that using secrets.GITHUB_TOKEN is correct for this workflow. In GitHub Actions, the built-in token is typically accessed via github.token (or is already available to API clients), and secrets.GITHUB_TOKEN may be redundant or behave differently in some contexts. Confirm the ShellCheck download logic actually reads GITHUB_TOKEN from env and that this change resolves the rate limiting. env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: yarn shellcheck Permissions Ensure the workflow’s permissions: are appropriately scoped for the added token usage (principle of least privilege). If the token is only needed for authenticated downloads, consider explicitly setting minimal permissions (e.g., contents: read) at the workflow/job level to avoid granting more access than required. env: GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} run: yarn shellcheck

📄 References redhat-developer/rhdh-chart/charts/orchestrator-software-templates-infra/templates/openshift-gitops/argocd-credential-template.yaml [0-2] redhat-developer/rhdh-chart/charts/orchestrator-software-templates/templates/tekton/tekton-tasks.yaml [45-52] redhat-developer/rhdh-operator/config/profile/rhdh/plugin-deps/tekton.yaml [45-52] redhat-developer/rhdh-chart/charts/orchestrator-software-templates/templates/tekton/tekton-tasks.yaml [117-151] redhat-developer/rhdh-operator/config/profile/rhdh/plugin-deps/tekton.yaml [117-151] redhat-developer/rhdh-chart/charts/orchestrator-software-templates/templates/tekton/tekton-tasks.yaml [91-116] redhat-developer/rhdh-operator/config/profile/rhdh/plugin-deps/tekton.yaml [91-116] redhat-developer/rhdh-chart/charts/orchestrator-software-templates/templates/tekton/tekton-tasks.yaml [1-21]

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-4049
• quay.io/rhdh-community/rhdh:pr-4049-93544c75

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

The image is available at:

• quay.io/rhdh-community/rhdh:pr-4049
• quay.io/rhdh-community/rhdh:pr-4049-57cea1b2

[subhashkhileri]

/lgtm

[albarbaro]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: albarbaro, subhashkhileri

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [albarbaro]

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