First off, thank you for considering contributing to DepShield! It's people like you that make the open source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
This section guides you through submitting a bug report for DepShield. Following these guidelines helps maintainers and the community understand your report, reproduce the behavior, and find related reports.
- Use a clear and descriptive title for the issue to identify the problem.
- Describe the exact steps which reproduce the problem in as many details as possible.
- Provide specific examples to demonstrate the steps. Include copy/pasteable snippets.
- Describe the behavior you observed after following the steps and point out what exactly is the problem with that behavior.
- Explain which behavior you expected to see instead and why.
- Include screenshots and animated GIFs which show you following the reproduction steps.
This section guides you through submitting an enhancement suggestion for DepShield, including completely new features and minor improvements to existing functionality.
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Provide specific examples to demonstrate the steps.
- Describe the current behavior and explain which behavior you expected to see instead and why.
- Fork the repo and create your branch from
main. - If you've added code that should be tested, add tests.
- If you've changed APIs, update the documentation.
- Ensure the test suite passes.
- Make sure your code lints.
- Issue that pull request!
-
Clone the repository
git clone https://github.com/rascal-sl/depshield.git cd depshield-cli -
Install dependencies
pnpm install
-
Build the project
pnpm build
-
Run tests
pnpm test -
Link for local testing
pnpm link --global
- We use TypeScript for type safety.
- We use ESLint and Prettier for code formatting.
- Please run
pnpm lintandpnpm formatbefore committing.
We follow the Conventional Commits specification.
feat: A new featurefix: A bug fixdocs: Documentation only changesstyle: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)refactor: A code change that neither fixes a bug nor adds a featureperf: A code change that improves performancetest: Adding missing tests or correcting existing testschore: Changes to the build process or auxiliary tools and libraries such as documentation generation
Feel free to ask questions in GitHub Discussions.