Gitless: a version control system
Git is, like many professional tools, something you simply got to learn.<p>But like with many professinal tools, you don&#x27;t need to know everything to get to work.<p>I don&#x27;t know all Photoshop or Ableton Live features, but I can improve my photos or create songs non the less.<p>With these commands you can already start your own repo and work on it locally:<p><pre><code>    git init &#x2F;&#x2F; crate new repo

    git status &#x2F;&#x2F; show which files are changed and which of them are staged

    git add -p &#x2F;&#x2F; add &quot;chunks&quot; of changed files to the stage

    git commit -m &quot;&lt;commit_msg&gt;&quot; &#x2F;&#x2F; commit everything added to the stage with a commit message

    git log &#x2F;&#x2F; show a list of commits

    git checkout &lt;file&gt; &#x2F;&#x2F; throw away all changes since the last commit (one file)

    git reset --hard &#x2F;&#x2F; throw away all changes since the last commit (all files)
</code></pre>
If you want to work with a repo from somewhere else like Github etc., you need a few extra commands:<p><pre><code>    git clone &lt;repo_url&gt; &lt;target_dir&gt; &#x2F;&#x2F; clone a remote repository locally

    git pull &#x2F;&#x2F; download and merge new commits in the remote repo that happened since the last clone&#x2F;pull

    git push &#x2F;&#x2F; uploading your own changes after a commit to the remote repo
</code></pre>
I think these 10 commands are all that is needed to get your own project into Git.<p>Yes, the more people are working on a project, the more commands you need, like creating a new branch and getting commits from one branch to another, or amending commits because you forgot something etc.<p>For a professional tool this isn&#x27;t too much, I think. The 10 commands I mentioned will be remembered in less than a week. Most of the rest isn&#x27;t needed often (maybe merge&#x2F;rebase and branch depending on how you intend to use Git), but they shouldn&#x27;t take too long either.