4 ms·
I really don't need a lot of fancy stuff in order for GitHub to be valuable to me or my organization. Honestly, I did not find much of the roadmap to be compell
by bob1029 6y ago
I really don't need a lot of fancy stuff in order for GitHub to be valuable to me or my organization. Honestly, I did not find much of the roadmap to be compelling.
For me, the core features that comprise my GH user story are:
- Code
- Pull Requests
- Issues & Labels
We also have limited use of Actions (for check builds) and heavy use of the API/Webhooks for integration with our own custom CI/CD tooling.
In my opinion, the biggest place where value should be added is in these 3 areas above. Some of the simplest ideas are the most powerful. We get an incredible amount of mileage out of basics like issues & labels. If there were additional aspects to issues similar to labels that could further enhance this experience, I would be very interested. Our entire development process revolves around issues to track tasks.
One of the things I've had in mind would be a way to build a markdown-defined webform template that can be used for populating highly-structured issues without requiring the user to edit a complex document each time.
For example, you could have CustomerTroubleTicketTemplate.md in a .github/issue_templates/ path, and then when you go to click New Issue, a down arrow could be provided that pops a list of all defined issue templates. Selecting one would present the user with a webform (as defined in the template markdown) that collects all required fields to create that issue. The issue could be created with labels/assignments/etc as defined in the markdown document. This would likely require enhancements to GFM.
Bonus points if there is some way to expose specific issue templates through public GH pages so that your customers can submit tickets against your private repositories even though they don't have direct access to your issue buckets. I think a very small step in this direction could obviate a lot of use cases people find with products like Zendesk (it would for us, anyways - we just funnel ZD tickets back into GH issues).