Stefan Zweifel

@deitch That's exactly the use case why I've created this project; and it does work as you described. Problems _sometimes_ appear when people use this Action in workflows that should...

I'm closing this issue. Usage of this action in forks has been documented in [the README](https://github.com/stefanzweifel/git-auto-commit-action?tab=readme-ov-file#use-in-forks-from-public-repositories). Thank you all for the feedback you've given in this thread.

Thanks for reporting. Currently not in front of a desktop, but I guess the problem is that actions/checkout is not used in your 2nd job, when you download the artifact....

I'm closing this issue now. Sorry for the very late response and for all your investigative research here. 💙

Thanks for your feedback/suggestion. Would you be able to share the **exact** error message you're receiving when running the action with `create_branch: true` and `push_options: '--force'`? Thanks!

Thank you @mvorisek. So the actual error you're getting is the following. > error: Your local changes to the following files would be overwritten by checkout: > test/unit/ns.html > Please...

I just also noticed, that you might run into issues with your workflow, if triggered by the scheduler: The `actions/checkout`-Action might checkout the repository in a detached state which could...

Hi @atodorov, As far as I know, the default token used by GitHub Actions can't have `workflows: write` permission. Probably another security measure by GitHub, to prevent _bad_ actions from...

I also assume that the error message "refusing to allow a **GitHub App** to create or update workflow `.github/workflows/main.yml` without `workflows` permission" is just a UX error. GitHub probably assumes...

@atodorov This seems like a reasonable explanation. 👍 Back to your original issue, have you tried the approach with a personal access token? I'm fairly certain that this will resolve...