Update schedule-update-actions.yml

[gitworkflows]

User description

Description

This PR fixes #

Notes for Reviewers

Signed commits

• [*] Yes, I signed my commits.

---

PR Type

configuration changes

---

Description

• Updated the GitHub Actions workflow file schedule-update-actions.yml to use secrets.ORG_REPO_TOKEN instead of secrets.PAT for the token field.
• Ensured consistency in token usage across the workflow steps.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	schedule-update-actions.yml Update token reference in GitHub Actions workflow                .github/workflows/schedule-update-actions.yml Updated the token field to use secrets.ORG_REPO_TOKEN instead of secrets.PAT. +2/-2

---

💡 PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

[codiumai-pr-agent-free]

PR Reviewer Guide 🔍

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

🧪 No relevant tests

🔒 No security concerns identified

⚡ No key issues to review

[codiumai-pr-agent-free]

PR Code Suggestions ✨

Category	Suggestion	Score
Possible issue	✅ Verify that the secret used in the workflow is correctly configured in the repository settings Ensure that the secret ORG_REPO_TOKEN is correctly set in the repository settings to avoid runtime errors. .github/workflows/schedule-update-actions.yml [18] +token: ${{ secrets.ORG_REPO_TOKEN }} - [Suggestion has been applied] Suggestion importance[1-10]: 7 Why: Ensuring that the secret is correctly set is crucial to avoid runtime errors, making this suggestion more important for the functionality of the workflow.	7
Best practice	✅ Use a more descriptive name for the secret to indicate its purpose clearly Consider using a more descriptive name for the secret ORG_REPO_TOKEN to clearly indicate its purpose, such as GITHUB_WORKFLOW_TOKEN. .github/workflows/schedule-update-actions.yml [18] -token: ${{ secrets.ORG_REPO_TOKEN }} +token: ${{ secrets.GITHUB_WORKFLOW_TOKEN }} [Suggestion has been applied] Suggestion importance[1-10]: 5 Why: The suggestion to rename the secret to something more descriptive is valid for clarity and maintainability, but it's not a critical issue.	5