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 npm was updated to 3.6.0 in master (nodejs/node#4958), some files were accidentally included that cause git issues checking out in Windows (nodejs/node#5094).
:: https://github.com/nodejs/node/issues/5094
ECHO OFF
FOR /F %%F IN ('git status --porcelain') DO (
git status
echo.
echo ERROR: Workspace cannot be cleaned, possible problem with committed file names
exit /b 1
)
ECHO ON
great, tho I'm wondering if we shouldn't @ that or something to prevent the "ERROR" text from showing up even when it's working fine, a quick scan or a ctrl-f will show up that text and may be easy to misread.
@nodejs/jenkins-admins
When npm was updated to 3.6.0 in master (nodejs/node#4958), some files were accidentally included that cause git issues checking out in Windows (nodejs/node#5094).
After
nodejs/node#5211nodejs/node#5369 or nodejs/node#5212 land, I plan to add this tonode-compile-windows
, to prevent the same problem from happening again:Tests:
The text was updated successfully, but these errors were encountered: