Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error message in Github Desktop #106

Closed
jitendravyas opened this issue Dec 2, 2016 · 4 comments
Closed

Error message in Github Desktop #106

jitendravyas opened this issue Dec 2, 2016 · 4 comments

Comments

@jitendravyas
Copy link

This tool gave error nicely in CLI but I just wanted to share that I use GitHub for desktop too along with CLI and some other developers in my team use SourceTree too.

Commit error in Github Desktop looks like this

image

Whole error code copied

/Users/jitendravyas/.zim/init.zsh: line 16: syntax error near unexpected token `('
/Users/jitendravyas/.zim/init.zsh: line 16: `  for wanted_module (${zmodules}); do'
�[?25l �[33m❯�[39m Running tasks for *.css
   �[33m⠙�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠹�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠸�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠼�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠴�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠦�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠧�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠇�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠏�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠋�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠙�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠹�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠸�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠼�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[33m⠴�[39m stylelint
�[?25l�[1000D�[K�[1A�[1000D�[K�[1A�[1000D�[K �[33m❯�[39m Running tasks for *.css
   �[31m✖�[39m stylelint
�[?25h
🚨  stylelint found some errors. Please fix them and try committing again.



�[4mapp/styles/main.css�[24m
 �[2m2:17�[22m  �[31m�[31m�[31m�[31m�[31m�[31m�[31m�[31m�[31m�[31m✖�[31m�[39m  Expected "#FFFFFF" to be "#ffffff"              �[2m�[2m�[2m�[2mcolor-hex-case�[22m        
 �[2m7:1�[22m   �[31m�[31m�[31m�[31m�[31m�[31m�[31m�[31m�[31m�[31m✖�[31m�[39m  Unexpected duplicate selector ".main-section"   �[2m�[2m�[2m�[2mno-duplicate-selectors�[22m



�[?25hpre-commit: 
pre-commit: We've failed to pass the specified git pre-commit hooks as the `lint-staged`
pre-commit: hook returned an exit code (1). If you're feeling adventurous you can
pre-commit: skip the git pre-commit hooks by adding the following flags to your commit:
pre-commit: 
pre-commit:   git commit -n (or --no-verify)
pre-commit: 
pre-commit: This is ill-advised since the commit is broken.
pre-commit: 
 (1)
@okonet
Copy link
Collaborator

okonet commented Dec 2, 2016

This should be hopefully fixed with the release of SamVerschueren/listr#33

@okonet
Copy link
Collaborator

okonet commented Dec 2, 2016

Actually, I just realized it has nothing to do with listr but with the fact that the GUI doesn't strip the ANSI codes. So, I'd report it to the GUI tool TBH.

Also, you can use https://github.com/ta2edchimp/opt-cli so your colleagues can opt out from using it.

okonet added a commit that referenced this issue Dec 7, 2016
* fix(tty): Force colors only when `process.stdout.isTTY` is true
* chore(dependencies): Upgraded listr to 0.9.0 that introduces nonTTY renderer fallback
* style: Changed emoji in case of failure

Closes #106
@alxpsr
Copy link

alxpsr commented Jul 5, 2022

Hey! I just got it from SourceTree client. Is it possible to fix it?

@alxpsr
Copy link

alxpsr commented Jul 5, 2022

Seems that i fixed it. Who will faced with it, just try to set variable NO_COLOR=1 before run command

NO_COLOR=1 npx lint-staged

see this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants