Issue:
Currently, the qcastel/github-actions-maven-release action requires an SSH private key for authentication when committing and pushing to the repository. GitHub Actions provides an automatically generated GITHUB_TOKEN for each workflow run that can be used for authentication with GitHub repositories.
It would be great if the action could support using the GITHUB_TOKEN for these Git operations instead of requiring the user to manually configure an SSH private key. This would simplify the workflow and improve security, as it removes the need to store and manage SSH keys.
Suggested Changes:
Allow the action to accept the GITHUB_TOKEN as an authentication method for performing Git operations like committing and pushing.
If the GITHUB_TOKEN is provided, use it for authentication instead of the SSH private key.
This change would make the action more compatible with GitHub’s default security model and streamline authentication for users who prefer to use GITHUB_TOKEN.
Additional Context:
The GITHUB_TOKEN is automatically provided by GitHub Actions and has the necessary permissions to interact with the repository. It is often preferred over using SSH keys for GitHub repository-related operations in Actions workflows.
Thank you for your consideration!
Issue:
Currently, the qcastel/github-actions-maven-release action requires an SSH private key for authentication when committing and pushing to the repository. GitHub Actions provides an automatically generated GITHUB_TOKEN for each workflow run that can be used for authentication with GitHub repositories.
It would be great if the action could support using the GITHUB_TOKEN for these Git operations instead of requiring the user to manually configure an SSH private key. This would simplify the workflow and improve security, as it removes the need to store and manage SSH keys.
Suggested Changes:
Allow the action to accept the GITHUB_TOKEN as an authentication method for performing Git operations like committing and pushing.
If the GITHUB_TOKEN is provided, use it for authentication instead of the SSH private key.
This change would make the action more compatible with GitHub’s default security model and streamline authentication for users who prefer to use GITHUB_TOKEN.
Additional Context:
The GITHUB_TOKEN is automatically provided by GitHub Actions and has the necessary permissions to interact with the repository. It is often preferred over using SSH keys for GitHub repository-related operations in Actions workflows.
Thank you for your consideration!