would be great so one doesn't have to forward to the {dev,community}/pureos channels
Description
Description
Event Timeline
Comment Actions
Is this a Tracker <--> Matrix channel? We already have #dev/pureos-changes so you don't mean that channel I assume.
Comment Actions
gitlab would be nice too but likely fine grained (e.g. calls -> calls channel, phosh/phoc/squeekboard -> phosh channel) - we had a bug for that somewhere in gitlab iirc, the above is about the pureos tracker only.
Comment Actions
Phabricator's API is called conduit. I can pull data from conduit and it looks like this;
{
"id": "1001", "phid": "PHID-TASK-4lpwd5rgworwzdwkbdg7", "authorPHID": "PHID-USER-kcngpcgit2gapkthvlnm", "ownerPHID": null, "ccPHIDs": [ "PHID-USER-kcngpcgit2gapkthvlnm" ], "status": "open", "statusName": "Open", "isClosed": false, "priority": "Needs Triage", "priorityColor": "violet", "title": "amber: postgresql-common securit update blocked due to downstream changes", "description": "As far as i can tell amber is lacking these security updates due to downstream changes in popstgresql-common:\n\nhttps://lists.debian.org/debian-security-announce/2019/msg00220.html\n\nSee https://master.pureos.net/synchrotron/\n```\npostgresql-common \tbuster/updates amber-security \t200+deb10u3 \t200pureos1 \tRequires manual merge of downstream changes with source. \n```", "projectPHIDs": [], "uri": "http://tracker.pureos.net/T1001", "auxiliary": [], "objectName": "T1001", "dateCreated": "1613384648", "dateModified": "1613384648", "dependsOnTaskPHIDs": []
}
The id, status, title and description look suitable for dumping into a Matrix channel. Is that okay @guido or are you looking for something more?