This is an enhancement request to support some kind of way to tell the plugin not to delete the git credentials after the checkout.

Today when ever I want to pull or push some changes from/to the remote git repository, I have to explicitly set the following configuration in may pipeline:

sh "git config --global user.name 'myuser'"
sh "git config --global user.email 'myuser@mycomp.com'"
# no pull/push works
sh "git push ..."

This has the major drawback, that now my pipeline script is bound to the credentials configured in my jenkins job. 

I therefore request a flag/option which I can enable so this information is set (or not removed after the checkout) by the bitbucket multibranch plugin.