Contributions in any form is most welcome. Some of the areas that could use improvements are
- Improve existing commands documentation (command descriptions, arguments descriptions etc.)
- Add documentation to existing commands that don't have one.
- Add new commands that have been missed from this list.
- Improved ways of presenting the information to the user.
Here are the general steps to setup a work environment and to get started
- Fork the repository and
git clone
your fork to thePackages/
directory. - Refer to the
.editorconfig
file (If you are not sure what's editorconfig file used for, you can read it over here) and setup the specific settings. I usually just create a Project for each package and set up project specific settings for them
{
"folders":
[
{
"path": "C:\\Users\\DELL\\AppData\\Roaming\\Sublime Text\\Packages\\CommandsBrowser"
},
{
"path": "C:\\Users\\DELL\\AppData\\Roaming\\Sublime Text\\Packages\\CommandsBrowser33"
}
],
"settings": {
"tab_size": 4,
"default_encoding": "UTF-8",
"default_line_ending": "unix",
"translate_tabs_to_spaces": true,
"ensure_newline_at_eof_on_save": true,
"trim_trailing_white_space_on_save": "all",
},
}
- Create a new branch off of the
master
and make your changes there. - Push the branch to your remote fork and then create a PR to
master
. - Wait for your PR to be reviewed. It may take some time to review so don't be disheartened if it's not done immediately.
- The PR get's merged to
master
and you have made an amazing contribution to keep the open source spirit alive ! You are awesome 😊