Oh ouiiiii ! A lightweight git repository hosting.
...lightweight 🤣
(via https://linuxfr.org/users/devnewton/liens/gitea-autohebergement-de-depots-git-facile)

All is explained here : Git can't watch all the files and detect changes between the Working Directory and the Staging Area. The node_modules directory is not ignored as expected.

I am using Ubuntu 20.04. Increasing the limit max_user_watches does not fix it for me (+ I have only 4GB of RAM).

Solution : putting the config from the default config file to the user one :

    "files.watcherExclude": {
        "**/.git/objects/**": true,
        "**/.git/subtree-cache/**": true,
        "**/node_modules/**": true,
        "**/.hg/store/**": true
    },

from the defaultSettings.json (Command palette : Preferences : Open default Settings (JSON)) to the userSettings.json (Command palette : Preferences : Open Settings (JSON)). WTF ?! But cool, it works 😎

A nice project dedicated to the highlighting of contributors

French documentation on the use of git. It seems complete.

• git clone --depth=3 will clone only the last 3 commits

À propos des différents rebase :

standard : synchroniser une branche par rapport à une autre
interactif : réécrire l'historique de la branche courante
onto : rattacher le premier commit d'une branche à la HEAD d'une autre branche

(shared by Riduidel : https://nicolas-delsaux.hd.free.fr/Shaarli/?TfMhpQ)

git merge-base branch1 branch2 will find the common ancestor commit of two branches.

Tip : check that only one commit is applied out of each command

git log branch1..common
git log branch2..common

• Cherry-pick the fix commit in a new branch (based on a common ancestor of the 2 branches) which will be then merged into them.
• Partial fix will be the same technique but the merge will be reverted in the feature branch before merging the feature branch in the master (see this)

Applying a range of commit in git : git cherry-pick fromCommit..ToCommit

Interactive cheatsheet with remise, working directory, index, local repository and remote repository columns
(from sebsauvage)

Well, the content is substantial

Related :

• AngularJS Git Commit Message Conventions

Improving the use of vim-fugitive of some shortcuts and command

GA = General availability (a release); should be very stable and feature complete

RC = Release candidate; probably feature complete and should be pretty stable - problems should be relatively rare and minor, but worth reporting to try to get them fixed for release.

M = Milestone build - probably not feature complete; should be vaguely stable (i.e. it's more than just a nightly snapshot) but may still have problems.

SR = Service Release (subsequent maintenance releases that come after major -RELEASE).

Software release life cycle illustrated

Créer des représentations graphiques de dépôt git.