denied by branch protections

[TomVasile]

Wondering what is the best way to work around branch protections?

Error: {"command":"git push origin HEAD","exitCode":1,"outputData":"","errorData":"remote: error: GH006: Protected branch update failed for refs/heads/dev.        \nremote: error: At least 1 approving review is required by reviewers with write access. 2 of 2 required status checks are expected.

[gautamkrishnar]

@TomVasile simply add a contents: write to the yaml file:

name: Github Action with a cronjob trigger
on:
  schedule:
    - cron: "0 0 * * *"
permissions:
  contents: write

jobs:
  cronjob-based-github-action:
    name: Cronjob based github action
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      # - step1
      # - step 2
      # - step n, use it as the last step
      - uses: gautamkrishnar/keepalive-workflow@v1 # using the workflow with default settings

You can also follow: gautamkrishnar/blog-post-workflow#67 (comment)

[julienloizelet]

Hi there,
I had the same error on my workflow (https://github.com/julienloizelet/ddev-playwright/actions/runs/5055025874/jobs/9072377298):

Error: {"command":"git push origin HEAD","exitCode":1,"outputData":"","errorData":"remote: error: GH006: Protected branch update failed for refs/heads/main.        \nremote: error: At least 1 approving review is required by reviewers with write access.        \nTo [https://github.com/julienloizelet/ddev-playwright.git\n](https://github.com/julienloizelet/ddev-playwright.git/n) ! [remote rejected] HEAD -> main (protected branch hook declined)\nerror: failed to push some refs to 'https://github.com/julienloizelet/ddev-playwright.git'\n"}

I already have a permissions: contents: write directive in the yaml file and even set the read and write permission to all worflows

Any idea of what I should try to make it work ? Thanks

[julienloizelet]

FYI,

if I disable the "Require a pull request before merging" rule, it works.

I would like to be able to make it work without disabling this kind of protection rule.

Any idea ?

[gautamkrishnar]

Unfortunately we can't get over this any way since this is a security feature. Only option is disabling it.

[rakuyoMo]

Or we could do it on an insignificant branch. This still guarantees that the repository is active, right?

[gautamkrishnar]

@rakuyoMo yap it will work