Are you looking for having the same information across the two tools or Asana will serve different needs than GitHub?
The goal, as Arielle has described it to me (though she can speak more specifically to this), is to be able to see the same information that’s in GitHub issues, in either Asana or Trello (not sure which one yet) so that one could use Asana or Trello as a kanban board to plan out work happening across multiple GitHub repos.
So it’s about supporting different users who don’t want to switch to a single tool or each tool is serving different needs?
In this case (again I’m paraphrasing what I’ve come to understand from Arielle) the goal is to get a kanban view into the GitHub issues because GitHub doesn’t provide a suitable kanban style board. So to your question, it’s more about each tool (GitHub vs Asana/Trello) serving different needs.