Default Commit Message Text

[JosephTLyons]

I made this exact same request on for GitHub Desktop, so I apologize if copying and pasting the text that I wrote in their required format here is frowned upon (please let me know, I will rewrite if that is an issue). There is more discussion with members of that team there as well.

Is your feature request related to a problem? Please describe.
It is not related to a problem, it is more related to convenience of use.

Describe the solution you'd like
On GitHub.com, if you edit a single file, the default commit text "Update filename" appears, which is actually quite useful in some cases when making small tweaks to non-code files (Markdown files, CHANGELOGs, etc.). It would be nice if this feature was available in Atom's Github Package. I would assume this feature would only be provided if the user had only one file selected; having multiple files selected would require the user to input a commit message and wouldn't allow for a default commit message (this is something that was discussed, in much more detail, on the GitHub Desktop issue I linked above).

Describe alternatives you've considered
Really there are none, a lot of times I just manually insert this default commit message text when making small, trivial commits.

Teachability, Documentation, Adoption, Migration Strategy
Users will be able to use this to increase their workflow speed. Many times, I find myself correcting 4 or 5 mistakes, back-to-back, and committing each one with default text of "Update filename". Having this text show up automatically would increase the speedy workflow of Atom's Github Package.

[pyamo]

Bump! This would be awesome, and is the main reason I'm still using github-desktop.

[flybd5]

Bump! Same here. Not impressed this still has not been addressed in TWO years.

[JosephTLyons]

Bump! Same here. Not impressed this still has not been addressed in TWO years.

Atom was essentially killed off. It gets a few extremely minor tweaks here and there, to make sure it still runs, but it doesn't have any serious active development on new features. I loved Atom, but gave up on it after it was essentially abandoned. I'm in VS Code now, about to jump to a new editor that is in alpha stages.

[flybd5]

I've tried VS Code. IMO it sucks, and I've been coding since the mid-70's. The fact that Atom does a great job even without the maintenance you think it needs speaks volumes about how much better it is than VS Code.

[JosephTLyons]

I've tried VS Code. IMO it sucks, and I've been coding since the mid-70's. The fact that Atom does a great job even without the maintenance you think it needs speaks volumes about how much better it is than VS Code.

Atom was awesome, but it suffered from many performance issues ... and being Electron-based made it resource hungry. I don't love VS Code myself; luckily others feel the same and are building more editors to choose from.