background preloader


Facebook Twitter

Version Control Best Practices. Commit Related Changes A commit should be a wrapper for related changes.

Version Control Best Practices

For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other team members to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits. Commit Often Committing often keeps your commits small and, again, helps you commit only related changes.

Don’t Commit Half-Done Work You should only commit code when it’s completed. Test Before You Commit Resist the temptation to commit something that you “think” is completed. Write Good Commit Messages Begin your message with a short summary of your changes (up to 50 characters as a guideline). Version Control is not a Backup System Having your files backed up on a remote server is a nice side effect of having a version control system. Use Branches. Faire son premier commit. Gérez vos codes source avec Git. Framaboard. Git - petit guide - no deep shit! Git - petit guide juste un petit guide pour bien démarrer avec git. no deep shit ;) par Roger Dudler (translation by KokaKiwi) Remerciements à @tfnico, @fhd, Namics this guide in english, deutsch, español, indonesian, italiano, nederlands, polski, português, русский, türkçe, မြန်မာ, 日本語, 中文, 한국어 installation Télécharger git pour Mac OSX Télécharger git pour Windows Télécharger git pour Linux créer un nouveau dépôt créez un nouveau dossier, ouvrez le et exécutez la commande git init pour créer un nouveau dépôt. cloner un dépôt créez une copie de votre dépôt local en exécutant la commande git clone /path/to/repository si vous utilisez un serveur distant, cette commande sera git clone username@host:/path/to/repository arbres ajouter & valider.

git - petit guide - no deep shit!

Git Workflows and Tutorials. The array of possible workflows can make it hard to know where to begin when implementing Git in the workplace.

Git Workflows and Tutorials

This page provides a starting point by surveying the most common Git workflows for enterprise teams. As you read through, remember that these workflows are designed to be guidelines rather than concrete rules. We want to show you what’s possible, so you can mix and match aspects from different workflows to suit your individual needs. Centralized Workflow Transitioning to a distributed version control system may seem like a daunting task, but you don’t have to change your existing workflow to take advantage of Git. However, using Git to power your development workflow presents a few advantages over SVN. Second, it gives you access to Git’s robust branching and merging model. How It Works Like Subversion, the Centralized Workflow uses a central repository to serve as the single point-of-entry for all changes to the project.

Developers start by cloning the central repository. Planning poker. Un article de Wikipédia, l'encyclopédie libre.

Planning poker

Utilisation[modifier | modifier le code] L'avantage principal du planning poker est de permettre à tous de s'exprimer librement. L'estimation serait meilleure parce que plusieurs personnes l'auront validée : des participants avec des niveaux d'expérience et d'expertise différents. De plus, cette technique favorise les échanges entre le responsable de produits et l'équipe de développement. L'estimation se fait en unités d'œuvre intitulées points de récits ou "journées idéales" (Ideal Day).

Les points de récits permettent d'obtenir une véritable mesure de complexité relative : les scénarios sont comparés entre eux. Les avantages de l'estimation en "journées idéales" (ou heures idéale en cas de faible granularité des tâches) sont parfaitement identiques à ceux des points de récits. La suite de Fibonacci est utilisée pour les évaluations. Déroulement[modifier | modifier le code] Liens externes[modifier | modifier le code] Git Reference. We've already seen how to use git log to compare branches, by looking at the commits on one branch that are not reachable from another.

Git Reference

(If you don't remember, it looks like this: git log branchA ^branchB). However, you can also use git log to look for specific commits. Here we'll be looking at some of the more commonly used git log options, but there are many. Take a look at the official docs for the whole list.