fix: Label PR Warning

[aimuz]

Signed-off-by: aimuz mr.imuz@gmail.com

What type of PR is this?

Uncomment only one /kind <> line, press enter to put that in a new line, and remove leading whitespace from that line:

/kind breaking
/kind bug
/kind cleanup
/kind documentation
/kind feature
/kind hotfix

What this PR does / Why we need it:

Which issue(s) this PR fixes:

Closes #

Special notes for your reviewer:

Warning: Unexpected input(s) 'repo-token', valid inputs are ['script', 'github-token', 'debug', 'user-agent', 'previews', 'result-encoding']

[agones-bot]

Build Succeeded 👏

Build Id: 190e7654-78bb-4b48-9935-3379962ebe6f

The following development artifacts have been built, and will exist for the next 30 days:

• image: us-docker.pkg.dev/agones-images/ci/agones-controller:1.33.0-dev-ad6d3ee-amd64
• image: us-docker.pkg.dev/agones-images/ci/agones-sdk:1.33.0-dev-ad6d3ee-linux-amd64
• image: us-docker.pkg.dev/agones-images/ci/agones-ping:1.33.0-dev-ad6d3ee-amd64
• image: us-docker.pkg.dev/agones-images/ci/agones-allocator:1.33.0-dev-ad6d3ee-amd64
• Linux C++ SDK (build): agonessdk-1.33.0-dev-ad6d3ee-amd64-linux-arch_64.tar.gz
• SDK Server: agonessdk-server-1.33.0-dev-ad6d3ee-amd64.zip

A preview of the website (the last 30 builds are retained):

• https://ad6d3ee-dot-preview-dot-agones-images.appspot.com/

To install this version:

• git fetch https://github.com/googleforgames/agones.git pull/3241/head:pr_3241 && git checkout pr_3241
• helm install agones ./install/helm/agones --namespace agones-system --set agones.image.registry=us-docker.pkg.dev/agones-images/ci --set agones.image.tag=1.33.0-dev-ad6d3ee-amd64

[markmandel]

@Kalaiselvi84 you are the expert on this one - this look good to you?

[Kalaiselvi84]

@Kalaiselvi84 you are the expert on this one - this look good to you?

I have tested it in my fork without including repo-token: ${{ secrets.GITHUB_TOKEN }}, and it is working fine. According to the documentation at https://docs.github.com/en/actions/security-guides/automatic-token-authentication, the secrets.GITHUB_TOKEN is automatically available to all workflows running in the repository, and there is no need to explicitly define or store it in the repository's secrets. However, it is important to consider the security implications, by not using this token could potentially grant unauthorized access to the repository. Nevertheless, since it is an open-source project, it should be acceptable to omit its usage. WDYT?

[aimuz]

In https://github.com/actions/github-script, the repo-token is not valid

https://github.com/actions/github-script#using-a-separate-github-token

[agones-bot]

Build Succeeded 👏

Build Id: d12da036-dec4-4dc4-8498-8b253d1db60f

The following development artifacts have been built, and will exist for the next 30 days:

• image: us-docker.pkg.dev/agones-images/ci/agones-controller:1.34.0-dev-956dc2b-amd64
• image: us-docker.pkg.dev/agones-images/ci/agones-sdk:1.34.0-dev-956dc2b-linux-amd64
• image: us-docker.pkg.dev/agones-images/ci/agones-ping:1.34.0-dev-956dc2b-amd64
• image: us-docker.pkg.dev/agones-images/ci/agones-allocator:1.34.0-dev-956dc2b-amd64
• Linux C++ SDK (build): agonessdk-1.34.0-dev-956dc2b-amd64-linux-arch_64.tar.gz
• SDK Server: agonessdk-server-1.34.0-dev-956dc2b-amd64.zip

A preview of the website (the last 30 builds are retained):

• https://956dc2b-dot-preview-dot-agones-images.appspot.com/

To install this version:

• git fetch https://github.com/googleforgames/agones.git pull/3241/head:pr_3241 && git checkout pr_3241
• helm install agones ./install/helm/agones --namespace agones-system --set agones.image.registry=us-docker.pkg.dev/agones-images/ci --set agones.image.tag=1.34.0-dev-956dc2b-amd64

[markmandel]

Sounds like this is a valid fix then.

[google-oss-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aimuz, markmandel

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [markmandel]

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