Skip to content

Instantly share code, notes, and snippets.

View abravalheri's full-sized avatar
💭
😆

Anderson Bravalheri abravalheri

💭
😆
  • University of Bristol
  • Bristol, UK
View GitHub Profile
git config --global alias.lola "log --graph --decorate --pretty=oneline --abbrev-commit --all"
@abravalheri
abravalheri / import.m
Created January 19, 2017 15:10 — forked from jaeandersson/import.m
Import a package into Octave using the syntax "import packagename.*"
function import(varargin)
% Import a package. Only entire packages can be imported currently.
error(nargchk(1, inf, nargin, 'struct'));
% Import the packages one-by-one
for i=1:nargin
import1(varargin{i});
end
end
function import1(pkgname)
@abravalheri
abravalheri / commit.md
Last active March 16, 2024 04:00 — forked from stephenparish/commit.md
RFC: Git Commit Message Guidelines

Commit Message Guidelines

In the last few years, the number of programmers concerned about writing structured commit messages have dramatically grown. As exposed by Tim Pope in article readable commit messages are easy to follow when looking through the project history. Moreover the AngularJS contributing guides introduced conventions that can be used by automation tools to automatically generate useful documentation, or by developers during debugging process.

This document borrows some concepts, conventions and even text mainly from these two sources, extending them in order to provide a sensible guideline for writing commit messages.