Recent git configuration change has broken our build


#1

Hi folks,

It appears that you’ve made some changes to the git configuration, which has caused an autotag script I created to fail.

warning: push.default is unset; its implicit value has changed in
Git 2.0 from 'matching' to 'simple'. To squelch this message
and maintain the traditional behavior, use:

  git config --global push.default matching

To squelch this message and adopt the new behavior now, use:

  git config --global push.default simple

When push.default is set to 'matching', git will push local branches
to the remote branches that already exist with the same name.

Since Git 2.0, Git defaults to the more conservative 'simple'
behavior, which only pushes the current branch to the corresponding
remote branch that 'git pull' uses to update the current branch.

See 'git help config' and search for 'push.default' for further information.
(the 'simple' mode was introduced in Git 1.7.11. Use the similar mode
'current' instead of 'simple' if you sometimes use older versions of Git)

fatal: The current branch master has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin master

Makefile:322: recipe for target 'circleci-deploy' failed

This started happening one or two days ago. Before this, the script could create tags w/o issue, and there was no message from git saying push.default is unset.

Is this a bug on your end, a temporary change, or permanent change? Cheers,

Ian


#2

That’s definitely new… Can you share that build with me? You can PM if necessary.


#3