scalvert

Git Commit Guidelines

We have very precise rules over how our git commit messages can be formatted. This leads to more readable messages that are easy to follow when looking through the project history. But also, we use the git commit messages to generate the AngularJS change log.

Commit Message Format

Each commit message consists of a header, a body and a footer. The header has a special format that includes a type, a scope and a subject:

scalvert

import Ember from 'ember';

class MyModel extends Ember.Object {
  constructor() {
    super();
    this._first = "Ricardo";
    this._last = "Mendes";
  }
  
  get first() {

scalvert

# Rename tags named foo-bar-#.#.# to v#.#.# and push the tag changes
git tag -l | while read t; do n="v${t##*-}"; git tag $n $t; git push --tags ; git tag -d $t; git push origin :refs/tags/$t ; done

scalvert

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});

scalvert

import Ember from 'ember';

export default Ember.Component.extend({
  isValid: Ember.computed('value', function() {
    return true;
  })
});

scalvert

import Ember from 'ember';
import hexColor from '../utils/hex-color';

const {
  Controller,
  computed
} = Ember;

export default Controller.extend({
  /**

scalvert

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});

scalvert

import Ember from 'ember';

export default Ember.Controller.extend({
  appName: 'Ember Twiddle'
});

scalvert

public class Tree<K, V>
    where K : class, IComparable<K>
    where V : class
{
    private Node<K, V> root;

    public V DepthFirstSearch(K key)
    {
        Stack<Node<K, V>> stack = new Stack<Node<K, V>>();
        root.Visited = true;

scalvert

public class Tree<K, V>
    where K : class, IComparable<K>
    where V : class
{
    private Node<K, V> root;

    public V BreadthFirstSearch(K key) 
    {
        Queue<Node<K, V>> queue = new Queue<Node<K, V>>();
        root.Visited = true;