Bugzilla

Thank you David for the explanation, it's much clearer now.

This next paragraph is more for :marco & :aryx :

We have now 2 options:
1. use a Phabricator webhook to trigger Taskcluster Hook with token, but we do not have a Harbormaster build target to update
    - the bot support this input for the analysis part
    - but it currently requires a build target to run publication
    - without a build target, we cannot post messages on the intergace top level, we'll be limited to comments.
  
2. use a Phabricator build plan that will provide a Harbormaster build target, but :
   - we cannot send any JSON Payload (not supported by Phabricator - see [this comment above](https://bugzilla.mozilla.org/show_bug.cgi?id=1935142#c3)) through Harbormaster build steps
   - taskcluster does not support query parameters in the URL in the `triggerHookWithToken` API endpoint
   - this will require a small update on the bot analysis code, but will reduce in complexity the `Revision` initial build

I think it would be better to stick with a Pahbricator build plan, as we have been using that for the past years, and do not want to change the messaging targeted at developers.
We need to find a way to trigger the Taskcluster Hook without a JSON payload & using query parameters:
- building a tiny web service that receives the HTTP query from Phabricator and converts it for Taskcluster
- do the same but using an existing service like [ifttt](https://ifttt.com/)
- support URL query parameters in `triggerHookWithToken`

I'll file a Github issue about that last step to get Taskcluster developers input.

Thank you David for the explanation, it's much clearer now.

This next paragraph is more for :marco & :aryx :

We have now 2 options:
1. use a Phabricator webhook to trigger Taskcluster Hook with token, but we do not have a Harbormaster build target to update
    - the bot support this input for the analysis part
    - but it currently requires a build target to run publication
    - without a build target, we cannot post messages on the intergace top level, we'll be limited to comments.
  
2. use a Phabricator build plan that will provide a Harbormaster build target, but :
   - we cannot send any JSON Payload (not supported by Phabricator - see [this comment above](https://bugzilla.mozilla.org/show_bug.cgi?id=1935142#c3)) through Harbormaster build steps
   - taskcluster does not support query parameters in the URL in the `triggerHookWithToken` API endpoint
   - this will require a small update on the bot analysis code, but will reduce in complexity the `Revision` initial build

I think it would be better to stick with a Pahbricator build plan, as we have been using that for the past years, and do not want to change the messaging targeted at developers.
We need to find a way to trigger the Taskcluster Hook without a JSON payload & using query parameters:
- building a tiny web service that receives the HTTP query from Phabricator and converts it for Taskcluster
- do the same but using an existing service like [ifttt](https://ifttt.com/)
- support URL query parameters in `triggerHookWithToken`

I filed a [Github issue](https://github.com/taskcluster/taskcluster/issues/7475) about that last step to get Taskcluster developers input.