Contribution: README section about having GH Actions trigger on fast-forwards

[0xangelo]

Hi, I'm willing to contribute a section to the README about triggering GitHub Actions after /fast-foward succeeds and looking for guidance on how best to add it.

TLDR: I think it's worth to tell users that they will want to use a personal access token for the action if they want their CI/CD to trigger after a successful /fast-forward

---

With the standard GITHUB_TOKEN, after a fast-forward succeeds, no workflows will be triggered. This may be confusing as the user might expect their CI/CD to trigger on any push to main for example.

The issue seems to be that GitHub doesn't trigger Actions on events created with GITHUB_TOKEN, to avoid recursive worflows. The solution seems to be using a personal access token, quoting from the release-please-action docs.

I tested it myself on one of my repositories and it seems to work. The only anomaly is that the bot's message will appear as if they were written by the owner of the personal access token. So the fast-forward action triggers on the final comment created by /fast-forward itself, and then cancels itself

[nwalfield]

Do I understand correctly that the workflows for the branch are triggered correctly, but workflows associated with the main branch are not triggered when the fast-forward action does the fast forward?

If so, I would welcome a patch explaining the problem, and a section explaining your workaround.

Thanks!

[0xangelo]

but workflows associated with the main branch are not triggered when the fast-forward action does the fast forward?

Exactly the above

If so, I would welcome a patch explaining the problem, and a section explaining your workaround.

Cool! I'll open a PR later this week and we can figure out where the best place in the README is

P.s.: thank you for this action! I'd buy you a coffee if I could

[nwalfield]

Thanks!