or
Caleb
completed
I think the Github issue tracker would be a very useful addition to the workflow. However I don't think there should be more than one venue for any one class of issue, and some types are probably better handled here on meta.

Here's my idea:

1. Enable the issue tracker, but disable blank issues and require picking from an issue template.
1. [Configure the new issue](https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser) wizard with prominent links back here to meta for types of issues that should be redirected here.
   - Anything site policy or community related (e.g. "Add downvotes" or "Add a site for Fuzzy Bears").
   - All user experience feature requests. ("Add tag descriptions")
1. Include explicit types and matching templates for the types of bugs that should be tracked there.
   - Security bugs ("XSS in ...")
   - Code style issues ("Change PHP code style to ...")
   - Deployment / workflow issues ("Remove NPM module source from repo")
   - Technical feature requests ("Add API method for...")
   - Other feature requests _only having been vetted on meta_, as cross link to a met post ("Implement feature discussed in meta post X")

A major thing that the issue tracker will do that meta posts here will not is collate commits with the issues they are related to. This makes it easier to collaborate as developers, track progress, discuss technical details, do code reviews, etc. It will also provide a home for things that would otherwise be noise on this Q&A site as they are simply not relevant or interesting to 95% of the intended audience of the actual site.

Note I'm happy to actually set this up but I'd like to see consensus or approval here first...
Top Answer
Tom V
> **Update 16 Jan, 2020** - The [TA GitHub issue tracker](https://github.com/topanswers/topanswers/issues) is now open.

---

Yes to this.

I came looking for this question as I noticed the Issues tab wasn't available on GitHub and would have asked for it to be enabled if I didn't find this question.

One of the benefits of using github issues is that potential contributors could just pick an issue if it's not in progress yet and create a pull request with a potential fix. (Although with the speed issues get fixed on this site it could be hard finding an issue to work on)
Answer #2
Jack Douglas
I know next to nothing about how GitHub issue trackers work, but based on what you have said here, it sounds like the way forward unless someone else has a sensible objection.

Initially at least we can continue to work on issues raised directly in comments here, but it would seem to make sense for the devs to raise the issue on GitHub ourselves with a link to the comment here when that happens.

> Note I'm happy to actually set this up…

Wonderful, it's great to have the extra expertise in areas we are weak, thank you.

> …but I'd like to see consensus or approval here first...

There is no particular rush so please wait until you feel any discussion here has run its course.
Answer #3
holmanb
I'll add a third voice of agreement. Github issue tracking is a key part of workflow on Github. You're likely to get plenty of developers happy to create tickets for bugs/features and you can use that to track future development and request/accept help for the site.
Can we open the issue tracker on Github?
Tom V replying to PeterVandivier
I don't mind. Time will tell what the etiquette turns out to be
PeterVandivier
obvs feel free to revert
PeterVandivier
@Tom i hope you'll excuse the highjacked edit. i figured as the  _Top Answer™️_, yours was the appropriate post to place the info on.
Caleb
There will always be some grey area in between, but for example my rants about how we really _need_ some analog of downvotes definitely need to be discussed here before the implementation becomes something to track there — and by the same token a bug report about something not quite working as advertised can skip any discussion here and go straight to bug status.
Caleb replying to David
Issues are open for business. And yes, your issue report could have gone there. I was describing the extreme ends, but anything UI related without any substantial effect on the polity or overall workflow of the site can probably go directly there without needing a meta post.
Caleb
Issues enabled, a couple templates proposed: https://github.com/topanswers/topanswers/pull/2
David replying to Jack Douglas
👍 That makes more sense to me - looks great! Thanks.
David replying to Jack Douglas
Ah!! So *that's* how it looks! I had seen that feature, but never thought my measly few stars would have bumped up my "voting power" already. 💪 ;)
Jack Douglas replying to David
that was a bug for sure — we've fixed that and the pluralisation, but also tweaked the 'x stars' placement to be to the left of the stars control. Do please let me know if you think it is an improvement or not.
Jack Douglas replying to David
It's one of our departures from SE — when your total stars go up [so does your voting power](/meta?q=232#a179)
David
@Caleb Under your #3, I'm not seeing a "template" for a simple(?) "bug" like the two noted above. Or more likely, that was simply assumed? Or are my couple of "bugs" above "interface issues"? 🤷‍♂️
David
Also, the star count doesn't show any number (blank) after clicking the star, but only after page refresh. Maybe that's a feature request, though. :)  
  
Hope this helps!
David
(2) As that screenshot shows, there are two star images showing up: both can be clicked, and both clicks contribute to the star count. I'm guessing that's not the way it should be.
David
I think this is [line 999 in get/community.php](https://github.com/topanswers/topanswers/blob/329754fa18d5b4dc0c175e7423362f9d24c92f0d/get/community.php#L999) but I could be wrong about that. I'm not familiar with that PHP notation, but shouldn't the echo for the `s` for plural simply be `!==`?
David
(1) When there is `1 star` it's reported as `1 stars`  as this screenshot shows: ![Selection_493.png](/image?hash=b841c477cb38cf49ce7fd2d05901ea9563d8beeafd680752c2b5274eb07a135f)
David
@Jack @Caleb Would be nice if the issue tracker was up. ;) There's something squiffy in the `stars` system—two things, actually.