Help
cancel
Showing results for 
Search instead for 
Did you mean: 
Ground Controller Lvl 2
Message 21 of 32

Re: Where do I post feature requests for Github ?

Feature request:

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

```console
$ some-command --flag
$ next-command
output
output
```

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
shell-problems.png
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
```console
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.
```console-clipboard-friendly
that behaved like this.

Ground Controller Lvl 1
Message 22 of 32

Re: Where do I post feature requests for Github ?

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.

 

Thanks!

Ground Controller Lvl 1
Message 23 of 32

Re: Where do I post feature requests for Github ? : Feature Request : Latest updaLinks on main page

Hi,

 

Nice to have links for the latest updates for the repos displayed on the Account's main page "entry" page.

 

Example 10 seconds recording of where the links to click should be.

 

Thanks,

Laurence.

Community Manager
Message 24 of 32

Re: Where do I post feature requests for Github ? : Feature Request : Latest updaLinks on main page

Hey @australium

 

Thanks for being here and for taking the time to record your feedback, I'll be sure to pass it along to the appropriate team. In the meantime, we're looking forward to seeing you around!


Best,
AndreaG

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Copilot Lvl 2
Message 25 of 32

Integrate Polls with Github?

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-

https://github.com/apex/gh-polls

 

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?

Community Manager
Message 26 of 32

Re: Integrate Polls with Github?

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 😀


Best,
AndreaG

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Copilot Lvl 2
Message 27 of 32

Re: Where do I post feature requests for Github ?

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: 

PR two commits.png

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:
PR one commit.png

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!

Ground Controller Lvl 1
Message 28 of 32

Re: Where do I post feature requests for Github ?

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.

Moderator
Message 29 of 32

Re: Where do I post feature requests for Github ?

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,


MChevy422

Mark helpful posts with Accept as Solution to help other users locate important info. Don't forget to give Kudos for great content!

Ground Controller Lvl 2
Message 30 of 32

Re: Where do I post feature requests for Github ?

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:

 

Capture.PNG