Alex Wolfe
Alex Wolfe
I'm also seeing this issue.
Did this ever find a resolution? I'm trying to do something like this, which is failing because the property is inaccessible: ``` const range = new String('1-10'); range.min = 1;...
Some other ideas from our fork of cut-release: - Ensure that the [local repo is tracking a remote](https://github.com/activeprospect/cut-release/blob/master/bin/cut-release.js#L250-L299) - Ensure that there are [no uncommitted changes locally](https://github.com/activeprospect/cut-release/blob/master/bin/cut-release.js#L472-L482) - Handle the...
> Ensure that local is not ahead of tracked branch :-1: - Why? If I am ahead of the remote, I am not going to have a push conflict. Seems...
> Ensure that there are no uncommitted changes locally. npm version (which we call) - already does that. What value is there in having cut-release do the same? We were...
Yeah. I'm not sure if testing that everything is pushed prior to cutting a new release is of value to other folks. This was an actual problem we had, so...
After looking at this more closely, I realized that our branch doesn't do what I said it does. It only checks that the remote isn't ahead. I guess it wasn't...
Is there any plan to merge this? Would you merge it if I contribute tests?
See pull #20.
Any thoughts on this? What will it take to get this merged?