Usually edits come in from GitHub pretty quickly thanks to webhooks and our cron jobs, but you're right that an edit feature in general is missing that's comparable to GitHub.

FWIW we do have a full issue edit page for certain ACL groups, we might want to look at expanding its use to include an "edit own" style check letting someone edit the base data they submitted regardless of their ACL role.

In which case are we saying we don't want people to use issues.joomla.org because they may as well use Github? I'm trying to encourage people to submit issues and resolve them and it's a little confusing as to which way is the preferred way at the moment.

Either one works, both end up with the same information. The basic difference is the tracker has categories, status tracking, the tests widget, and a way to give users (mainly bug squad members) permissions to manage items on GitHub through its API without giving everyone full management access on the repo.

Ah I see, ok got it. Very clever stuff. Ok well my issue is neither here nor there, if it's in any way difficult then other things should be prioritised instead.