`Term.branch_head` should add any required `.monitor` file

[talex5]

Currently if you want to check the status of a project that isn't itself being built by the CI, you need to add the .monitor file manually to tell the bridge to watch it. This should be done automatically.

Will wait for #384 to be merged before changing this, to avoid conflicts.

[avsm]

This would still be really useful to have for rapid bootstrapping of fresh CI setups.

[avsm]

Another thought: it would help with unprivileged monitoring to be able to put in a poll: daily (or similar) into the monitor file to make it not establish a webhook, and to regularly check for updates (as it does on restarting) instead.

[samoht]

you can already put a .dirty in there and write your own loop to write it daily.

[avsm]

aha, this might be something for the datakit-ci process to help with then? An unprivileged mode where instead of writing a .monitor file it uses .dirty on a loop but can operate without GitHub privilege.

[talex5]

For bootstrapping fresh CI setups, you might prefer to use the local bridge: https://github.com/docker/datakit/tree/master/bridge/local

[avsm]

LOCAL BRIDGE!!!! Yes!!