Closed shunjid closed 4 years ago
Hmm the Reference already exists
is likely a result from trying to create a branch that already exists. I thought that we check for that, but seems we do not cover all cases.
Can you tell the steps to reproduce the problem?
Hi @gr2m ,
To reproduce the problem we first need to
head
's value.Afterwards, the plugin returns Reference already exists
and throws an error.
Why did you close the issue? Did you figure out the problem?
@gr2m
Yeah. I was about to explain. There were some internet issues. Extremely sorry for late response.
In my code, I figured out that I wasn’t handling Promise in a correct way. Moreover there were some issues with caching in the environment I was running the program which were causing unexpected warning.
Once again, I wanna thank you for developing this awesome plugin. 😊
Hi there,
You've created an awesome plugin :tada: . In one of my projects, I've been trying to use your plugin and successfully created a PR with some changes. But there is an issue.
Let's say, I haven't merged that newly created branch by your plugin and did some change again in my code. In that case, my desired change is not getting committed to the head branch. In this scenario, I'm getting some error like this below:
My question:
Thanks :smile: , Have a good day !