Version bumping working on local repository but not in Github actions

[yarnabrina]

Hello, I am trying to learn how to automate the version bumping process. I followed the documentation and locally both pyproject.toml and my other configured files are getting updated correctly. However when I try to use this is Github Actions, it is failing with some git issues.

This is my current configuration:

[tool.bumpversion]
allow_dirty = false
commit = true
current_version = "0.0.5"
ignore_missing_files = false
ignore_missing_version = false
message = "Bump version: {current_version} → {new_version}"
parse = "(?P<major>0|[1-9]\\d*)\\.(?P<minor>0|[1-9]\\d*)\\.(?P<patch>0|[1-9]\\d*)"
regex = false
replace = "{new_version}"
search = "{current_version}"
serialize = [
  "{major}.{minor}.{patch}",
]
tag = false
[[tool.bumpversion.files]]
filename = "src/package_name_to_import_with/metadata.json"

And this is the error I am getting on Github job:

Failed to run ['git', 'commit', '-F', '/tmp/tmp6t4jneu7']: return code 128, output: b''

I have enabled verbose flag and ensured that it is running on a non-default branch so that pre-commit related restrictions should not apply. But these seem to be insufficient.

Can someone please suggest with this problem?

[coordt]

I think the issue is that, by default, GitHub actions does not have permission to commit or push the commits back to the repo.

While, I am not an expert on GitHub Actions, I created a personal access token with Repo capabilities. That token is passed into the workflow in the repo's Settings -> Secrets and Variables -> Actions section under "Repository Secrets"

To deal with the pre-commit restrictions, I also use commit_args = "--no-verify" in the configuration

I may need to write up something in the docs...

[yarnabrina]

I have specifically configured user name and email for git to use, so I hoped at least commit should work. Can you kindly take a look at the workflow file please? For some reason even commit seems to fail. Since it works locally I think (rather hope) no verify is not required, but I'll verify that once more.

I may need to write up something in the docs...

This will be much appreciated, thanks for considering. If I can make it work for ny repo, I can share the steps if you want.