Description:
Implemented the version bump workflow using the GitHub action referenced in issue #112.
Key Changes:
The workflow uses the FragileTech/bump-version action.
Paths-ignore is set to VERSION to prevent the workflow from triggering when only the VERSION file is updated.
Important Notes:
Personal Access Token (PAT) Requirement: This workflow requires a PAT to function. Once generated, the login field in the workflow file should be updated with the username of the account that created the PAT.
Tested Successfully: To ensure the workflow functions as expected and to prevent unintentional behavior (like a fork bomb), I've tested this implementation on my private repository.
Next Steps:
Generate a PAT with the necessary permissions.
Update the login field in the workflow file with the username associated with the PAT.
Implement Version Bump Workflow (closes #112)
Description:
Implemented the version bump workflow using the GitHub action referenced in issue #112.
Key Changes:
FragileTech/bump-versionaction.VERSIONto prevent the workflow from triggering when only theVERSIONfile is updated.Important Notes:
loginfield in the workflow file should be updated with the username of the account that created the PAT.Next Steps:
loginfield in the workflow file with the username associated with the PAT.