CI autofix_prs: false for pre-commit.ci
State: closed

Somehow, this autoupdate job doesn't trigger all the workflows. I don't know why, because [the same workflow in PyMC3](https://github.com/pymc-devs/pymc3/pull/4466) works just fine.

From [this action's README](https://github.com/technote-space/create-pr-action), all the actions have commit email and commit name set - setting them is all I can think to try at the moment. @afeld any ideas? Maybe there's a different workflow that should be used instead?

Labels:
name: CI
description: Continuous Integration

Comments:
Sorry for the slow response. The difference between pandas (e.g. https://github.com/pandas-dev/pandas/pull/40439) and pymc3 (e.g. https://github.com/pymc-devs/pymc3/pull/4466) is that the former is sending the pull request from @github-actions. [More info, with workaround.](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#triggering-new-workflows-using-a-personal-access-token)
Thanks @afeld , that's useful! I'll get back to this
@jreback shall we try making a new token? I'll paste the instructions I sent one of the PyMC3 maintainer, as it worked for them (though we may have to delete the current ACTION_TRIGGER_TOKEN first as something likely went wrong with that one)

---

1. click 'Settings' on your profile icon:

![image](https://user-images.githubusercontent.com/33491632/111900020-014bc580-8a28-11eb-9020-90bb28b73f40.png)

2. click 'developer settings'

![image](https://user-images.githubusercontent.com/33491632/111900039-17f21c80-8a28-11eb-921c-8a66b15f3d32.png)

3. select 'personal access tokens', and then 'generate new token'

![image](https://user-images.githubusercontent.com/33491632/111900046-23ddde80-8a28-11eb-8b40-d533bac14cfd.png)

4. call it 'ACTION_TRIGGER_TOKEN' and then check the 'repo' checkbox

![image](https://user-images.githubusercontent.com/33491632/111900050-2c361980-8a28-11eb-8bbd-28062589d99d.png)

5. you'll see a token generated. copy it to the clipboard

![image](https://user-images.githubusercontent.com/33491632/111900063-4112ad00-8a28-11eb-80f2-9f8f622740b3.png)

6. go to the pandas-dev/pandas repo, and go to 'settings'

![image](https://user-images.githubusercontent.com/33491632/111900091-5daee500-8a28-11eb-97ce-be235772b927.png)

7. click 'secrets' and then 'new repository secret'

![image](https://user-images.githubusercontent.com/33491632/111900106-6e5f5b00-8a28-11eb-9814-3e79ff46a268.png)

8. name it ACTION_TRIGGER_TOKEN, and paste the value you copied in step 5 in value. Then, 'add secret' and that should be everything 

![image](https://user-images.githubusercontent.com/33491632/111900108-76b79600-8a28-11eb-9952-db5279962ff0.png)

I've repurposed this to set `autofix_prs: false` in the settings for [pre-commit.ci](https://pre-commit.ci/) - if we enable it then we can get rid of .github/workflows/comment_bot.yml, .github/workflows/autoupdate-pre-commit-config.yml, and .github/workflows/pre-commit.yml
> I've repurposed this to set `autofix_prs: false` in the settings for [pre-commit.ci](https://pre-commit.ci/) - if we enable it then we can get rid of .github/workflows/comment_bot.yml, .github/workflows/autoupdate-pre-commit-config.yml, and .github/workflows/pre-commit.yml

sounds good
Awesome - @jreback do you want to re-enable pre-commit-ci then? It should be in settings -> integrations