You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow custom fields in issues (e.g. library version, language version,
operating system)
Make fields required (e.g. library version or link to a test case; making such
information mandatory would dramatically reduce noise)
Show contributing guidelines before opening an issue (yet another noise
reduction)
Show count of how many people will be notified next to the issue creation
button
View notifications without marking them as read
Allow disabling automatically marking them as read, so they have to be
manually marked as read.
Flag notifications or issues for future follow up (i.e. create a
personal/private flag)
Turn unintuitive search query system into GUI
Auto-search for "similar issues" based on the words in the issue title and
body when the issue is created, to prevent dups - similar to how Stack
Overflow already works
Select multiple issues and then close with a single comment
Ability to merge issues
Ability to move issues to other repos
Explicitly eliminate content-free replies like "+1", or convert them into a
rating system for issues so watchers aren't constantly notified! A separate
rating system would be nice too.
Voting system for proposals
Something that surfaces votes at an issue-viewing level that can be sorted
easily by counts/labels. This allows distilling the highest priority bits to
work on.
Add support for custom reply messages (e.g. “Can’t reproduce...”, “Please
attach a test case...”, “Please use forum for questions...”, etc.)
Add support for default placeholder message when opening an issue (similar to
what Google Code did — “What steps would reproduce a problem? … Expected
result: … Actual result: … etc.”)
Better tools for addressing tracker spam comments/issues
Don’t make it so easy to submit bad PRs → For example, remove the default
commit title when creating a commit from the GitHub UI. When I see “Update
readme.md”, I know I’m in for annoyance.
Ability to block users from an organization.
Allow assigning issues to anyone who has contributed to the issue, not just
project maintainers. This way issues can be assigned back to the OP when more
info is needed.
Support explicitly marking an issue/pull request as “Needs Revision”/”Needs
More Info” and then have the tag automatically removed once someone comments
on the issue/updates the code in the pull request.
Support “private labels” for issues. Users should be able to add private
labels to any issue, even if it’s a project they don’t maintain. They should
then be able to use them for querying/filtering.
Allow automation rules, such as automatically notifying or closing when issues
have been untouched for a long time.
Support linear histories in the big green merge button. The project maintainer
should be able to specify whether merge commits should be created, or the
change should be rebased on top of master.
Support the ability to change the target branch in a PR without having to
close and reopen a new one -- This way you do not have to lose the comments
and discussion that may have happened in the original PR
Allow more than one format for reviewing issues. For example, displaying all
issues within a spreadsheet format, sortable by columns.
The text was updated successfully, but these errors were encountered:
https://github.com/dear-github/dear-github
Features at the time of writing this:
operating system)
information mandatory would dramatically reduce noise)
reduction)
button
manually marked as read.
personal/private flag)
body when the issue is created, to prevent dups - similar to how Stack
Overflow already works
rating system for issues so watchers aren't constantly notified! A separate
rating system would be nice too.
easily by counts/labels. This allows distilling the highest priority bits to
work on.
attach a test case...”, “Please use forum for questions...”, etc.)
what Google Code did — “What steps would reproduce a problem? … Expected
result: … Actual result: … etc.”)
commit title when creating a commit from the GitHub UI. When I see “Update
readme.md”, I know I’m in for annoyance.
project maintainers. This way issues can be assigned back to the OP when more
info is needed.
More Info” and then have the tag automatically removed once someone comments
on the issue/updates the code in the pull request.
labels to any issue, even if it’s a project they don’t maintain. They should
then be able to use them for querying/filtering.
have been untouched for a long time.
should be able to specify whether merge commits should be created, or the
change should be rebased on top of master.
close and reopen a new one -- This way you do not have to lose the comments
and discussion that may have happened in the original PR
issues within a spreadsheet format, sortable by columns.
The text was updated successfully, but these errors were encountered: