CI: Fix "Unexpected input" warning

[RanitMukherjee]

Notes for Reviewers

• Moved token: Relocated GH_ACCESS_TOKEN to the actions/checkout step.
• Removed invalid input: Deleted the unsupported token parameter from git-auto-commit-action to clear the runner warning.

Result: Maintains authentication while resolving the "Unexpected input(s) 'token'" log warning.

This PR fixes #608

Signed commits

• Yes, I signed my commits.

[gemini-code-assist]

Summary of Changes

Hello @RanitMukherjee, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a CI warning by refining how access tokens are managed within GitHub Actions workflows. It ensures that repository operations are correctly authenticated while eliminating an "Unexpected input" log message caused by an invalid parameter in a specific action.

Highlights

• Token Relocation: The GH_ACCESS_TOKEN has been moved to the actions/checkout step to ensure proper authentication within the CI workflow.
• Invalid Input Removal: The unsupported token parameter was removed from the git-auto-commit-action to resolve an "Unexpected input" warning in the CI logs.

Changelog

• package-lock.json
  • Updated the version of @meshery/schemas from 0.8.123 to 0.8.124.

Ignored Files

• Ignored by pattern: .github/workflows/** (1)
  • .github/workflows/generate-artifacts-from-schemas.yml

Activity

• The author provided specific notes for reviewers detailing the token relocation and the removal of an invalid input parameter.
• The author confirmed that all commits are signed.
• This pull request aims to fix issue [CI] GitHub Workflow Warning: unexpected "token" annotation #608.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to fix a CI warning, as described in the title and description. However, the only change included is a version bump in package-lock.json. The described CI file changes do not appear to be part of this pull request. While the version update is not problematic, the main goal of the PR is not addressed by the current changes. Please add the relevant workflow file changes to this PR.