A list of the features we would love to see Github support, in order to build better applications around the product!
Custom Issue Meta Data through the API
Having the ability to push your own payload to an issue would be phenomenal. We currently have to use label hacks in order to support velocity, timers, priority, and other features that the Trax app provides. If we could just push a small amount of custom metadata to Github, we wouldn't need to use these hacks (or in the future create our data store).
Default Issue Templates
Issue templates are great! Porting them to every single project is not. It would be nice if we could define them once for the organization and easily apply them to any repo.
Default Labels
Just like issue templates, it would be really cool to be able to define default labels for our organization that automatically applied to our repositories. This feature was actually one of our first reasons for building Trax.
ASCII Sorting for Labels
We had to get clever with our label hacks, using --- prefixes and ••• text in labels so that we can force certain labels to the top of the label-select dropdown. It seems like a silly, but also a simple request. It's also one you probably know the pain of if you've worked on a monolithic repo with over a dozen labels.
Make H1 Headers a wee bit smaller
I mean, all of these headers are basically top level. Do they all need to compete so much for attention? Am I supposed to break semantics and use an H3 header so that I can have a more visually pleasing result? We already have section headers and titles. I think all the headers can come down a couple of points in size.
[ ] Checkbox support on Headers
Because as a user, I want to be able to write a proper user story and description, without using an overcrowded list.
More spacing between List Items
@nat you said on the live-stream today we have a voice
I love this open door approach and it seems very genuine and I'm super excited. I've been using Github for years. I'm even a part of the Developer Program, but that's only added value in the form of a cute little badge above my bio. I have no idea where I'm supposed to submit ideas! On a typical community project, it would be a feature request on a repo, but which one?
A list of the features we would love to see Github support, in order to build better applications around the product!
Custom Issue Meta Data through the API
Having the ability to push your own payload to an issue would be phenomenal. We currently have to use label hacks in order to support velocity, timers, priority, and other features that the Trax app provides. If we could just push a small amount of custom metadata to Github, we wouldn't need to use these hacks (or in the future create our data store).
Default Issue Templates
Issue templates are great! Porting them to every single project is not. It would be nice if we could define them once for the organization and easily apply them to any repo.
Default Labels
Just like issue templates, it would be really cool to be able to define default labels for our organization that automatically applied to our repositories. This feature was actually one of our first reasons for building Trax.
ASCII Sorting for Labels
We had to get clever with our label hacks, using
---prefixes and•••text in labels so that we can force certain labels to the top of the label-select dropdown. It seems like a silly, but also a simple request. It's also one you probably know the pain of if you've worked on a monolithic repo with over a dozen labels.Make H1 Headers a wee bit smaller
I mean, all of these headers are basically top level. Do they all need to compete so much for attention? Am I supposed to break semantics and use an
H3header so that I can have a more visually pleasing result? We already have section headers and titles. I think all the headers can come down a couple of points in size.[ ] Checkbox support on Headers
Because as a user, I want to be able to write a proper user story and description, without using an overcrowded list.
More spacing between List Items
methodInSomeFile()can get really crowded.@nat you said on the live-stream today we have a voice
I love this open door approach and it seems very genuine and I'm super excited. I've been using Github for years. I'm even a part of the Developer Program, but that's only added value in the form of a cute little badge above my bio. I have no idea where I'm supposed to submit ideas! On a typical community project, it would be a feature request on a repo, but which one?