Autosquash not triggered when the PR is validated about autosquash

[Kineolyan]

For the record, after switching the tests to CircleCI instead of one Github Action, it is working like a charm.

[tibdex]

Yes workflows can be scheduled. You could also try adding:

autosquash/.github/workflows/autosquash.yml

Lines 30 to 36 in 3ded0d9

	- uses: tibdex/autosquash@v2
	with:
	# We can't use the built-in secrets.GITHUB_TOKEN yet because of this limitation:
	# https://github.community/t5/GitHub-Actions/Triggering-a-new-workflow-from-another-workflow/td-p/31676
	# In the meantime, use a personal access token with repo access.
	# See https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line
	github_token: ${{ secrets.AUTOSQUASH_TOKEN }}

at the end of your existing GitHub CI workflow.

[tibdex]

Seems related to #22 (comment) since your PR status is blocked too. You can set the ACTIONS_STEP_DEBUG secret to true in your repo and try to reproduce the issue to get more details about what event triggered the action and in which state your PR was at that time.

[tibdex]

In fact the issue is that checks created by GitHub Actions will not trigger workflows so Autosquash doesn't rerun after your build action.

[Kineolyan]

Thanks for the feedback. I'm watching the answer as you are. Feel free to close this issue if you want.

[boredland]

hi! does this mean, currently the branches marked as "autosquash" aren't merged after the checks are green? thats a bummer...

[tibdex]

Depends how your checks became green.

• If it was triggered by a GitHub Action, the Autosquash workflow won't execute as explained in #25 (comment).
• If it was triggered by an external action such as a successful CircleCI/Travis CI workflow, then the Autosquash workflow will execute as confirmed in #25 (comment).

[boredland]

one of my checks is a github workflow (a ci pipeline). I wanted to merge as soon as all checks (including that one) are green.

[boredland]

would it be possible to run the autosquash action on a schedule to come around that for now?

[boredland]

thanks @tibdex ! But when I run it on a schedule, I get this totally different error:
##[error]Cannot destructure property `name` of 'undefined' or 'null'.

So I'd guess you extract some information from the github event that isn't there on a schedule obviously. The github_token I have already set, but I think I doesn't help the situation, that another gh action marks green.

[boredland]

totally overread that I should add that to the existing workflow! Makes sense, will try. Still think handling schedule-events would make sense.

[tibdex]

You can use https://github.com/marketplace/actions/github-app-token as an often better workaround to secrets.GITHUB_TOKEN's limitations than a personal access token.