Skip to content

ci: fix PR not triggering workflows by switching back to pytestbot access token#10346

Merged
bluetech merged 1 commit intopytest-dev:mainfrom
bluetech:ci-pat
Oct 7, 2022
Merged

ci: fix PR not triggering workflows by switching back to pytestbot access token#10346
bluetech merged 1 commit intopytest-dev:mainfrom
bluetech:ci-pat

Conversation

@bluetech
Copy link
Member

@bluetech bluetech commented Oct 6, 2022

The builtin actions token is not allowed to trigger further workflows. So when we create a PR using that token, the PR checks don't run, and a maintainer must close & open the PR to make them run. This is quite annoying, so switch back to the "machine user" approach.

Fixes #9554.

…cess token

The builtin actions token is not allowed to trigger further workflows.
So when we create a PR using that token, the PR checks don't run, and a
maintainer must close & open the PR to make them run. This is quite
annoying, so switch back to the "machine user" approach.

Fixes pytest-dev#9554.
@bluetech
Copy link
Member Author

bluetech commented Oct 6, 2022

I remember the CHATOPS token has the required permissions, but not 100% sure, so once this is merged I'll make sure to test that it actually works (must be merged to the main branch before I can test it).

@nicoddemus
Copy link
Member

Thanks @bluetech for tackling this!

@bluetech bluetech merged commit ed5d4e1 into pytest-dev:main Oct 7, 2022
@bluetech
Copy link
Member Author

bluetech commented Oct 7, 2022

Marking this for backport just to test it out, but not going to actually backport it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Backport workflow: Use access token to run CI on PRs?

2 participants