Claudio Jolowicz

If we want to get fancy with this, it may get tricky to do it in cupper and noxfile alone. So there's this crazy idea: Go ahead with some form...

See also https://browniebroke.com/blog/gh-action-pre-commit-autoupdate/

@eyllanesc I'm wondering if it's possible to use pre-commit.ci for updates only, without actually running hooks. Most of our hooks are system hooks, so pre-commit.ci can't run them. In fact,...

That's an interesting idea. But AFAIU manual triggers apply to the entire workflow, not an individual step. They also don't support additional conditions. Or am I missing something here?

Unfortunately steps cannot be conditional on the presence of a secret, see #512. We might still document the correct flow to set up a repository without creating a failed workflow...

A workaround would be to copy the secret to an environment variable first, see https://github.com/actions/runner/issues/520#issuecomment-860043020. As pointed out later in that thread, this could result in leaking the secret in...

Hi @pauleveritt thanks for chiming in here! I'm hesitant to change the secret name to `PYPI_API_TOKEN`, as it would potentially break people who keep their existing projects up-to-date with the...

You're welcome!

> A workaround would be to copy the secret to an environment variable first, see [actions/runner#520 (comment)](https://github.com/actions/runner/issues/520#issuecomment-860043020). As pointed out later in that thread, this could result in leaking the...

Thanks, this looks interesting. This action could be run after the `pre-commit` session in the Tests workflow. ~~Does it handle external contributions gracefully? The action should not fail the workflow...