Where do I post feature requests for Github ?


Would you kind folks at GitHub be so inclined as to implement a feature to notify users when a commit is made to master? Currently I see two extremes; 1) get notified of  everything 2) get notified of releases. A couple of the repos I follow don’t do releases (a lot of the ‘awesome-<insert-thing>’ repos) but I’d like to know when a cool entry is added to the repo.

Best Intentions,

Daniel Okey-Okoro.


Often when I make a PR, the changes I made only make sense in light of one or more other unchanged files.

I would like the ability to tag other unchanged files as “of interest” in my PR so they show up with an empty diff in the PR, to save reviewers the hassle of scrounging around on their own to get the whole picture.

P.S. It won’t let me tag this feature request as “feature request”, so I’ve had to tag it as “featur3 request”.


Many times I come across bad code in repos. We need a way to flag the repo as 💩 with a button at the top of the page, just like stars, except negative.

This will help the community identify terrible code.


I’m trying to use Github projects to manage a new project, but I’m finding that it’s missing some key features:

  • Need to pin a note or issue to the top of a column.
  • Need to add a description to a column that appears below the title and above the cards.
  • Need to set up project and/or column automation to act on issues with certain labels. It would be great to have a project focused on a particular label or set of labels.
  • Need to have project and/or column automation itself apply labels to issues. e.g. when an issue is moved from “To Do” to “Doing”, the “in-progress” label is applied to the issue.
1 Like

I’m not a massive user of Github but whenever I do come to look around and possibly download a project or part of it I’m wondering why you don’t list the SIZE of the repo or the current folder when showing the Clone or Download zip button on the web gui. 

Maybe its somewhere else in the interface ??   But when I go to clone or download I would really like to know if I’m looking at a 30KB or 200MB  download.


1 Like

Being able to take a poll on a feature, issue or any other requests is a demanding feature nowadays. Right now there exists a low-key workaround which has many limitations due to 3rd party security policies-


I wish this feature was available accross all github repositories so as to make use of it to the full potential.

P.S. Another obvious thing to ask is why there is no feature request section in github’s contact page?

1 Like

Would love if you could render Swift Color literals as colors. Thanks! 

Hi there github! 

I couldn’t find a dedicated feature request page, but I wanted to know if there was a way to change the default behaviour for squashing and merging Pull Requests from branches that have one commit vs Pull Requests from branches that have many commits. 

If I make a PR from a branch with many commits, before merging, github defaults the squash merge commit message to be the title of the PR. Here’s a screenshot with an example: 

But if I make a PR for a branch that has one commit only, the commit message for the squash merge commit will default to that commit message:

Would it be possible to change this default behaviour, or to have an option to change it? The reason is most devs on our team mistakingly forget to update the commit message for the PR if the branch has only one commit, because we usually have more than one commit in our branches. We use the squash merge commit messages as a changelog with ticket/task numbers, so if this happens we either have to revert and recreate the PR or edit the history of the master branch (which is of course undesirable!) 

If I’ve posted this in the wrong place, please let me know and I’ll be happy to repost it somewhere else!

1 Like

Hey @udayraj123, Thanks for your feedback, although we do not have a dedicated page in the contact support page, you are welcome to email your requests to support@github.com or drop them as a new topic here. And Thanks for the feedback! I’ve taken your suggestion and passed it along to the appropriate teams. Thanks again for reaching out :grinning:

1 Like

Hi @andreagriffiths11 , I think that pull request for projects wiki is a really good and interesting feature 

1 Like

Allow switching between header and implementation files where appropriate.

I would like to see github have the feature that when browsing source code that has header and implementation files that you could quickly browse to the header from the implementation and vica versa. This would only make sense when the header and implementation files were in the same directory. But if there was a file called myclass.cpp and one called myclass.h then I should be able to switch between these without going back to the file directory.

1 Like

Hello @aranm

Thank you for your feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive.

I’ve logged your feature request in our internal feature request list. Although I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.

Once again, thank you for your input it is greatly appreciated,


https://help.github.com/en/articles/about-code-owners is a good feature for a large team.

But I think it can be better by adding owners on the changed files list so Owners knows which files they should review

On the Insights > Forks page could you add some sort of indicator for forks whether the main branch is ahead/behind/equal with the original repos main branch?

Of course you can click through each one and see what the heading says, but that’s far from conventient:


It would be really handy to be able to find Forks that are ahead to ask people to contribute back, etc.

(Note: Default might be a better term than main, I’m not sure exactly what it’s refered to in github parlance.)


I’d like to forbid people from publicizing their organisation membership.

We want people to be able to use their private github accounts but have concerns over individuals being linked to the organisation publically.  When they’re added to the org via SSO, it defaults to private (good) but I want to forbid individuals from making their membership publicly visible via my org security settings:


__FEATURE REQUEST__: Can we have a simple way to refer to tags/releases in comments.  We can refer to sha’s, pr’s and issues easily enough but the other day I wanted to write…

> Available as of 0.5.0

And while it wasn’t arduous to link the remark to the release in question using markdown it was more out of the than I expected.  It seems like this is the kind of thing we’d want a simple inline way of doing, much like referencing a commit.


P.S. it’d be great if GitHub used an issues board for this kind of thing instead of this forum.


Hello @tdreid

Thank you for your feedback! We’re always working to improve GitHub and the GitHub Community Forum, and we consider every suggestion we receive. I’ve logged your feature request in our internal feature request list.

Though I can’t guarantee anything or share a timeline for this, I can tell you that it’s been shared with the appropriate teams for consideration.

Once again, thank you for your input!

Greatly appreciated


1 Like

Feature request:

In github-flavored markdown, I’m often posting shell snippets like

$ some-command --flag  
$ next-command  

I include the dollar sign at the beginning as a “shell prompt” to indicate that those are the lines I expect my users to copy and paste, and NOT the lines of output. Unfortunately, the dollar signs are selectable as part of the text
so the user must seperately copy and paste both some-command --flag and next-command into their terminal, instead of being able to copy and paste the entire series of shell commands in a single selection.

It would be cool if either the

snippet label were modified to have the desired selection behavior I described with regard to lines that began with a dollar sign, or alternatively if there were another snippet label e.g.  
that behaved like this.

Feature request here!

To be able to combine a tweet into Github Markdown directly from Twitter that includes the look and feel of a tweet.

Also to be able to post a tweet to Twitter about updates - for example the commit messages - for a repository given the Twitter information.


1 Like