Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 36 additions & 0 deletions .github/ISSUE_TEMPLATE/bug_report_general.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,36 @@
---
name: Bug report - Other bugs
about: Create a report to help us improve

---

<!-- This template is meant for GENERAL bug reports.
Please be as descriptive as possible
-->

### Work environment

<!-- Filling this table is mandatory -->

| Questions | Answers |
|-----------------------------|-----------------------------------------|
| Which component is breaking | Vulnerability detection issue, etc. |
| Source of LAVA | `git clone`, pip, release binaries etc. |
| Version/git commit | v5.0.1, \<commit hash> |

<!-- OTHER BUGS -->

### Expected behavior

### Actual behavior

### Steps to reproduce the behavior

- Use code markdown `CODE` to make your code visible

<!-- ADDITIONAL CONTEXT -->

### Additional Logs, screenshots, source code, configuration dump, ...

Drag and drop zip archives containing the Additional info here, don't use external services or link.
Screenshots can be directly dropped here.
17 changes: 17 additions & 0 deletions .github/ISSUE_TEMPLATE/feature_request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
name: Feature request
about: Suggest an idea for Vanir

---

### Feature

- [ ] New Vanir scanner
- [ ] Technical Debt remediation
- [ ] Other (elaborated below)

**Describe the feature you'd like**
A clear and concise description of what you want to happen.

**Additional context**
Add any other context about the feature request here.
23 changes: 23 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
<!-- Filling this template is mandatory -->

**Your checklist for this pull request**
- [ ] I've documented or updated the documentation of every function and struct this PR changes.
- [ ] I've added tests that prove my fix is effective or that my feature works (if possible)

**Detailed description**

<!-- Explain the **details** for making this change. Is a new feature implemented? What existing problem does the pull request solve? How does the pull request solve these issues? Please provide enough information so that others can review your pull request. -->

...

**Test plan**

<!-- What steps should the reviewer take to test your pull request? Demonstrate the code is solid. Or what test cases you added. Ideally, have some tests and/or screenshots that can replicate results -->

...

**Closing issues**

<!-- put "closes #XXXX" in your comment to auto-close the issue that your PR fixes (if any). -->

...