If it’s worth saying, but not worth its own post, here's a place to put it.
If you are new to LessWrong, here's the place to introduce yourself. Personal stories, anecdotes, or just general comments on how you found us and what you hope to get from the site and community are invited. This is also the place to discuss feature requests and other ideas you have for the site, if you don't want to write a full top-level post.
If you're new to the community, you can start reading the Highlights from the Sequences, a collection of posts about the core ideas of LessWrong.
Addendum: Each Github issue gets synced to a non-public Asana card (previously to Trello, but the same logic applies) via the automation service Unito. So as a comparatively efficient solution, one which hopefully wouldn't take too much time, you could presumably set up a reverse Unito automation which closes Github issues when their corresponding Asana card is concluded. Ideally including an automatic Github comment (maybe incl. automatic tags) to explain why and how the issue was closed (e.g. resolved, not planned).
This sounds relatively straightforward to do: Unito allows setting up two-way sync workflows (rather than the current one-way sync workflow), and neither of their pages on Asana and Github imply any significant limitation to this two-way sync functionality.
They even have a full help article on this exact integration here, and its motivation matches my original request:
create tasks in Asana based on specific GitHub issues that will then be synced together in real-time, so that as you make changes in one place, you’ll see them reflected in the other.
You can use this workflow to streamline software development management; the ticketing progress; or to align comments, assignees, custom fields, and more.
EDIT: Possibly this 2-way sync with Asana already exists, and what's needed instead is to manually or automatically update all the old stale tasks which were still synced to Trello. Unito has a help article for the Github-Trello integration here.
If it’s worth saying, but not worth its own post, here's a place to put it.
If you are new to LessWrong, here's the place to introduce yourself. Personal stories, anecdotes, or just general comments on how you found us and what you hope to get from the site and community are invited. This is also the place to discuss feature requests and other ideas you have for the site, if you don't want to write a full top-level post.
If you're new to the community, you can start reading the Highlights from the Sequences, a collection of posts about the core ideas of LessWrong.
If you want to explore the community more, I recommend reading the Library, checking recent Curated posts, seeing if there are any meetups in your area, and checking out the Getting Started section of the LessWrong FAQ. If you want to orient to the content on the site, you can also check out the Concepts section.
The Open Thread tag is here. The Open Thread sequence is here.