Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

https://github.com/Jahenr/CheatSheets

Cheat Sheets for many well know systems. Featured on https://github.com/szabgab/awesome-for-non-programmers
https://github.com/Jahenr/CheatSheets

begginer-friendly beginner-project chill community documentation documentation-tool first-timers-friendly git markdown open-source

Last synced: about 1 month ago
JSON representation

Cheat Sheets for many well know systems. Featured on https://github.com/szabgab/awesome-for-non-programmers

Lists

README 

        
# CheatSheets



This repo is small project that is a central place for the most common commands used for systems we may use in work/projects.



It can allow new starters to contribute to projects on Github and get used to Git tools and commands.



You don't really need any coding experience as this is more of a documentation project, so no stress. Please feel free to contribute anytime you can, its appreciated.



I am still learning about Github and Git myself and want to get involved more within the open source community, so please feel free to give any advice or recommendations via an issue request.



---



To add stuff to this repo it is best to fork this repo, git clone your fork of the repo, create a branch and make changes, push them to your fork and then open a PR.



High level Steps include:



1. [Fork the repo and git clone your fork](https://docs.github.com/en/get-started/quickstart/contributing-to-projects)

2. [Create your branch](https://www.atlassian.com/git/tutorials/using-branches)

3. [Make your changes and commit them with a quick message of what was added](https://www.atlassian.com/git/tutorials/saving-changes/git-commit)

4. Push your changes and branch to your forked repo

5. [Open a PR so your changes can be reviewed and merged into the main project](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request)



The changes will be reviewed and if all is well, merged into master.



**Tip**: Remember to add the main project as upstream and do a `git pull` or `fetch` to keep your local fork up to date with the main project, before you commit and push any changes to your forked version ready for a PR.



Here is [a handy guide with more detail for clarity](https://stefanbauer.me/articles/how-to-keep-your-git-fork-up-to-date)



---



Please have a search (`ctrl + f`) to see if the categories/commands or options have already been added, please do not duplicate already added entries. If possible try to group similar bundles of commands with each other.



The structure should be as followed.



Category or sub category:



```bash

    # Quick explanation of command

    	Command

```



e.g



Linux:



```bash

    # List files and Directories.

    	ls

    		#Options include.

    			-l = List

    			-h = Human readable file/directory size

    			etc



    # List files in a list, shows file size in human readable format and shows hidden files.

    	ls -lha

```



Looking at the example above the category/sub category name ends in a colon, then the command description is indented 1 tab (_8 Spaces_) below. The command itself is then indented 2 tabs (_16 Spaces_), the options title if applicable is indented 3 tabs (_24 Spaces_) and the options themselves indented 4 tabs (_32 Spaces_).



This is how the layout should be for the listed commands etc., please follow the same structure throughout each cheat sheet.



Thank you and have fun 😉