Rename "Github: Push" to "Git: Push"

[epelc]

Prerequisites

• Put an X between the brackets on this line if you have done all of the following:
  • Reproduced the problem in Safe Mode: http://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
  • Followed all applicable steps in the debugging guide: http://flight-manual.atom.io/hacking-atom/sections/debugging/
  • Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
  • Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
  • Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description

[Description of the issue]

The Github: Push command is really just pushing via git(it works if your remote is hosted elsewhere). I'd recommend renaming this and the force push command to avoid confusion between git and GitHub.

Expected behavior: [What you expect to happen]
Git: Push

Actual behavior: [What actually happens]
GitHub: Push

Reproduces how often: [What percentage of the time does it reproduce?]

Versions

Atom 1.18 and 1.19beta0

You can get this information from copy and pasting the output of atom --version and apm --version from the command line. Also, please include the OS and what version of the OS you're running.

Additional Information

Any additional information, configuration or data that might be necessary to reproduce the issue.

[BinaryMuse]

The main problem here is that the command names are automatically generated from the internal package-name:command-name strings, and Atom's convention is to always use the package name as the first half of the command. Otherwise, we would conflict with a package named git that implemented a push command.

We've discussed this in the past, and you can see the discussion here: #363 (comment)

Thanks for the issue!

[epelc]

Thanks @BinaryMuse, I wasn't aware how the command names were generated.