fix(commits): Use --no-color for git branch-command

When `git branch --contains ${commit}` has colored output the `inHistory` check failed
fix: use travis-deploy-once to reenable travis-pro support
2016-11-21 09:46:44 -03:00 · 2016-11-17 15:40:21 -03:00
2 changed files with 2 additions and 2 deletions
@@ -15,7 +15,7 @@
  "dependencies": {
    "@bahmutov/parse-github-repo-url": "^0.1.0",
    "@semantic-release/commit-analyzer": "^2.0.0",
-    "@semantic-release/condition-travis": "^5.0.0",
+    "@semantic-release/condition-travis": "^5.0.2",
    "@semantic-release/error": "^1.0.0",
    "@semantic-release/last-release-npm": "^1.2.1",
    "@semantic-release/release-notes-generator": "^2.0.0",
@@ -13,7 +13,7 @@ module.exports = function (config, cb) {

  if (!from) return extract()

-  exec('git branch --contains ' + from, function (err, stdout) {
+  exec('git branch --no-color --contains ' + from, function (err, stdout) {
    var inHistory = false
    var branches
Author	SHA1	Message	Date
PAkerstrandandStephan Bönnemann	f239f2f402	fix(commits): Use `--no-color` for `git branch`-command When `git branch --contains ${commit}` has colored output the `inHistory` check failed	2016-11-21 09:46:44 -03:00
Stephan Bönnemann	2be6e5d34a	fix: use travis-deploy-once to reenable travis-pro support	2016-11-17 15:40:21 -03:00