At the moment, the first-party GitHub integration for Asana is an external app that uses App Components to attach GitHub PRs to tasks.
This means that if you’re writing your own integrations that work with Asana and the GitHub integration, it is technically possible but kind of hacky to fetch the PR associated with a task via API, and not possible at all to write to the field via API; it can only be done with the Asana UI.
It would be really useful if there was a proper API somewhere that would allow custom code to integrate with the Asana GitHub integration. This would make it easier to use Asana together with GitHub from custom scripts in developers’ local environments, in CI workflows, and so on.
Hi @Daisy_Brenecki , thank you for a great insight and welcome to the forum
From my side, the main constraint is that the PR-related data is scoped to the GitHub integration, which the user explicitly authorizes to access their GitHub during the auth flow. Bringing a third integration into that exchange would require it to be authorized to both Asana and GitHub at the same time.
In other words, the underlying question becomes: “How can one integration interact with data that is owned by another integration?” Practically and policy-wise, that isn’t something to be allowed, since users grant consent for Asana to access their third-party data, not for “all other current and future connected apps” to do so.
That said, nothing holds back from building an app that implements the GitHub functionality you need and then adding the extra behaviors you’re after.
Also, since I believe GitHub integration is strategic and maintained internally, we’d love to hear specific enhancement ideas, we’ll be happy make sure they get in front of the relevant team.
