Trigger phrases don't trigger from PR description

[jekhardt]

Comments work okay, but it would be very helpful to have the description also be a source to check for trigger phrases. We have a pull request description template contains options of available trigger phrases, but they don't do anything unless the author always makes a new comment. It would be helpful to save a few hundred copy pastes each day.

[benpatterson]

Based on this description, I wonder, are new commits not sufficient for kicking off the build for you? What you're describing may not be available in GitHub webhooks.

[benpatterson]

Clarifying note. I think the author wants:

• builds via webhook
• only build by trigger phrase
• [enhancement] recognize trigger phrase on commit message

[davetobin]

@jekhardt I'm not sure if the author would like the trigger phrase to be recognised on commit message or on the initial description added @benpatterson Please clarify.

I've noticed that when the initial comment is added when opening a PR it is treated as ghprbPullLongDescription and not ghprbCommentBody meaning it does not trigger the job from the trigger phrase. It would be very useful to add this functionality where it will check the ghprbPullLongDescription for the trigger phrase also. If this is not the same request I will open a new issue.

[jekhardt]

FWIW, this was for the pull request body description field in GitHub to be a source to check for patterns. PullLongDescription sounds like the right request.