49 lines
2.0 KiB
Markdown
49 lines
2.0 KiB
Markdown
<!--
|
|
Thank you for your interest in and contributing to Detection Rules!
|
|
There are a few simple things to check before submitting your pull request
|
|
that can help with the review process. You should delete these items
|
|
from your submission, but they are here to help bring them to your attention.
|
|
-->
|
|
# Pull Request
|
|
|
|
*Issue link(s)*:
|
|
|
|
<!--
|
|
Add Related Issues / PRs for context. Eg:
|
|
Related to elastic/repo#999
|
|
Resolves #123
|
|
If there is no issue link, take extra care to write a clear summary and label the PR just as you would label an issue to give additional context to reviewers.
|
|
-->
|
|
|
|
## Summary - What I changed
|
|
|
|
<!--
|
|
Summarize your PR. Animated gifs are 💯. Code snippets are ⚡️. Examples & screenshots are 🔥
|
|
-->
|
|
|
|
## How To Test
|
|
|
|
<!--
|
|
Some examples of what you could include here are:
|
|
* Links to GitHub action results for CI test improvements
|
|
* Sample data before/after screenshots (or short videos showing how something works)
|
|
* Copy/pasted commands and output from the testing you did in your local terminal window
|
|
* If tests run in GitHub, you can 🪁or 🔱, respectively, to indicate tests will run in CI
|
|
* Query used in your stack to verify the change
|
|
-->
|
|
|
|
## Checklist
|
|
|
|
<!-- Delete any items that are not applicable to this PR. -->
|
|
|
|
- [ ] Added a label for the type of pr: `bug`, `enhancement`, `Rule: New`, `Rule: Deprecation`, `Rule: Promote`, `Rule: Tuning`, `Hunt: New`, or `Hunt: Tuning` so guidelines can be generated
|
|
- [ ] Added the `meta:rapid-merge` label if planning to merge within 24 hours
|
|
- [ ] Secret and sensitive material has been managed correctly
|
|
- [ ] Automated testing was updated or added to match the most common scenarios
|
|
- [ ] Documentation and comments were added for features that require explanation
|
|
|
|
## Contributor checklist
|
|
|
|
- Have you signed the [contributor license agreement](https://www.elastic.co/contributor-agreement)?
|
|
- Have you followed the [contributor guidelines](https://github.com/elastic/detection-rules/blob/main/CONTRIBUTING.md)?
|