You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When publishing we do a deep check on a clean "git status" object, and check it against the actual result of git.status on the path to the project we provide.
assert.deepStrictEqual(compare,CLEAN_REPO,'The git repo must be clean (committed and pushed) before releasing!')
Motivation
The issue is that no matter what the differences of the two objects is, the error prints: The git repo must be clean (committed and pushed) before releasing!
My issue was that my branch was named "main" instead of the default "master". But the error message was throwing me off.
I propose to print the result of assert.deepStrictEqual, as it provides the expected vs. received, so it would flag up if the tracking or any other properties on those objects didn't match.
Alternatively, if we only care about the ahead & behind properties to determine the git status, we could only compare those 2 properties.
🚀 Feature Proposal
When publishing we do a deep check on a clean "git status" object, and check it against the actual result of
git.status
on the path to the project we provide.here:
releasify/lib/commands/publish.js
Line 76 in 52ffba8
Motivation
The issue is that no matter what the differences of the two objects is, the error prints:
The git repo must be clean (committed and pushed) before releasing!
My issue was that my branch was named "main" instead of the default "master". But the error message was throwing me off.
I propose to print the result of
assert.deepStrictEqual
, as it provides the expected vs. received, so it would flag up if thetracking
or any other properties on those objects didn't match.Alternatively, if we only care about the
ahead
&behind
properties to determine the git status, we could only compare those 2 properties.Example
or something like:
The text was updated successfully, but these errors were encountered: