Support for publish_branch that is the same as the triggering branch?

Currently, we’re getting the following error for this CI config:

Setup auth token
  [INFO] setup GITHUB_TOKEN
  ##[error]Action failed with "You deploy from PMLB2.0 to PMLB2.0"

From https://github.com/peaceiris/actions-gh-pages/issues/245, it sounds like this is the intended behavior to:

When users set a publish_branch that is the same as a branch triggered by the workflow, this action stops the deployment to protect the branch.

In our case, we use CI to regenerate some files. The use case is similar to linting. Imagine CI is used to lint files that should be committed back to the same branch.

What are the reasons that publishing to the triggering branch is forbidden? Is there a workaround?

[peaceiris]

That is the goal. When CI changes a file, we want that change to be pushed back to the triggering branch.

This action does not support this use case.

I just recommend you to use git commands.

- name: update
  run: |
    git add .
    git commit -m "update"
    git push origin YOUR_BRANCH

[github-actions[bot]]

This issue has been LOCKED because of it being resolved!

The issue has been fixed and is therefore considered resolved. If you still encounter this or it has changed, open a new issue instead of responding to solved ones.

<div align="right">Log | Bot Usage</div>