W. Trevor King 567aab405b nmbug: Handle missing @upstream in is_unmerged ... If we don't have an upstream, there is nothing to merge, so nothing is unmerged. This avoids errors like: $ nmbug status error: No upstream configured for branch 'master' error: No upstream configured for branch 'master' fatal: ambiguous argument '@{upstream}': unknown revision or path not in the working tree. Use '--' to separate paths from revisions, like this: 'git <command> [<revision>...] -- [<file>...]' 'git rev-parse @{upstream}' exited with nonzero value You might not have an upstream if you're only using nmbug locally to version-control your tags.		2014-07-16 19:31:28 -03:00
..
nmbug	nmbug: Handle missing @upstream in is_unmerged	2014-07-16 19:31:28 -03:00
nmbug-status	nmbug-status: Optionally load the header and footer templates from the config	2014-07-15 20:15:23 -03:00
status-config.json	nmbug-status: make output title and blurb configurable	2014-03-23 08:33:34 -03:00