Fetch entire branch

[packagespace]

This allows to push auto-fixes to the branch instead of being in detached head state (closes #23)

I have tested my fork on one of my projects and I can confirm that it works.
However, there's a separate issue: the bot's commit and push trigger a new CI pipeline immediately, which can mask failures from later stages of the original user-initiated pipeline.

[jasonkarns]

However, there's a separate issue: the bot's commit and push trigger a new CI pipeline immediately, which can mask failures from later stages of the original user-initiated pipeline.

Wouldn't the bot's commit also trigger those same downstream jobs? So if there was a failure in the original push, it would reoccur in the bot's push? (or it could be resolved, but either way, the status would be "correct")

[jasonkarns]

We can't assume the event that started the job is a pull_request event. It could just as easily be a push event, workflow_dispatch, scheduled cron run, workflow_call, or something else entirely.

[jasonkarns]

@packagespace did you intend to publish your fork to the marketplace? Would you consider renaming your fork so that the official action can be published under that name?

[packagespace]

However, there's a separate issue: the bot's commit and push trigger a new CI pipeline immediately, which can mask failures from later stages of the original user-initiated pipeline.

Wouldn't the bot's commit also trigger those same downstream jobs? So if there was a failure in the original push, it would reoccur in the bot's push? (or it could be resolved, but either way, the status would be "correct")

As far as I remember, the bot's commit did not trigger the same jobs. I'm not using this on any project anymore but I've attached a screenshot of what happened.

As you can see, only the GitGuardian job was triggered. It could be that it just needs to be fixed with some configuration.

@packagespace did you intend to publish your fork to the marketplace? Would you consider renaming your fork so that the official action can be published under that name?

I've de-listed it, no idea publishing my fork would block anything from anyone else from being published.