Contribution Guide
See original GitHub issueI’m trying to fix #233. I cloned the repo and ran npm run test
- and it modified all the files in test/colorize-results
directory. I don’t think this should happen. Are the tests out of date? Am I doing something wrong while running tests?
It would be really nice to have a contribution guide which can, if not answer these questions, point me in a correct direction on how to add fixes/features.
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Contributing to Open Source Projects — contribution-guide ...
This document provides a set of best practices for open source contributions - bug reports, code submissions / pull requests, etc.
Read more >Setting guidelines for repository contributors - GitHub Docs
You can create guidelines to communicate how people should contribute to your project. About contributing guidelines. To help your project contributors do good ......
Read more >Contribution Guide - The Go Programming Language
This document is a guide to help you through the process of contributing to the Go project, which is a little different from...
Read more >Contribution Guidelines - Creative Commons Open Source
We have a standard set of labels across all projects, documented here. Here are some of the ones that are most relevant to...
Read more >How to Build a CONTRIBUTING.md
A CONTRIBUTING.md file, in your open source repository or site, provides potential project contributors with a short guide to how they can help...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
That will definitely be it, changing tokens will most likely break the tests as they check the token output.
You should remove that for the instance that’s running the tests.
Looks like this is because I have
in my VS code settings.
If I comment out that setting, it works fine. My VS Code settings shouldn’t affect tests. I’m not sure if this is a VS Code issue.