refactor: gst is short for Git Status

[ronnuriel]

Signed-off-by: Ron Nuriel rnuriel@gsitechnology.com

Description

As the title say, gst is short for git status and not stash. In my opinion gs is more fit for git stash and gst for git status. As you can see there is a project about git status that using gst. gst-github-project

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• [ ] My code follows the code style of this project.
• [ ] If my change requires a change to the documentation, I have updated the documentation accordingly.
• [ ] I have read the CONTRIBUTING document.
• [ ] If I have added a new file, I also added it to clean_files.txt and formatted it using lint_clean_files.sh.
• [ ] I have added tests to cover my changes, and all the new and existing tests pass.

[ronnuriel]

Hey, @NoahGorny :)

[davidpfarrell]

Greetings,

First off, thanks for using Bash-it and for taking the time to create a PR !

Managing alias files is tough since in the end, you're essentially subjecting the many (ie. 1000's of people who Bash-it) to the whims of the few (ie. the dozen or so contributors to this alias file since its creation).

You can never please everyone - You can only hope you've offered something useful enough.

I'm going to vote against this PR:

• I personally use gs for status daily, but I only use stash maybe once or twice a month
• gs has represented "git status" for at least twelve years

I've often lamented that I wish we had a dedicated site for capturing the public's opinion of aliases that can surface the statistics, possibly even automating the creation of standard alias files based on global opinion, while allowing users to personalize the files to match their preferences.

I may have to spend some time trying to build such a site ...

In the meantime, my recommendation is to either keep the changes in your local bash-it folder, or reset the aliases after bash-it initializes.

I personally do the latter for a few aliases, but if you're also using the alias-completion plugin, you may need to fix up the completions for the aliases you modify ...