if git-pick creates a new branch git-pick have to set the upstream branch
git push --set-upstream origin ${branchname}

The dependency update-notifier was updated from 2.5.0 to 2.6.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

update-notifier is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Your Greenkeeper Bot 🌴

could you please create a new release? :)

git cherry-pick have a flag "-m" for merging merge-commits.
git-pick currently doesn´t support cherry-pick merge-commits, please add support for this.
maybe with --merge | -m ? :)

Version 0.13.3 of husky just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As husky is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

• says successfull, when merge-conflict and stay´s in failed branch
• stdout / stderr