Project: Beats (Observability and Analysis / Observability)
File: PULL_REQUEST_TEMPLATE.md

<!-- Type of change Please label this PR with one of the following labels, depending on the scope of your change: Bug Enhancement Breaking change Deprecation Cleanup Docs --> <!-- Mandatory Explain here the changes you made on the PR. Please explain: WHAT: patterns used, algorithms implemented, design architecture, message processing, etc. WHY: the rationale/motivation for the changes This text will be pasted into the squash dialog when the change is committed and will be a long term historical record of the change to help future contributors understand the change, please help them by making it clear and comprehensive, they may be you. If the commit title is adequate to describe both of these things, The text here may be omitted or replaced with "See title". The title of the PR will be used as the commit message title when the merge is made and the "See title" marker will be removed if present. The text here and the PR title will be subject to the PR review process. --> <!-- Mandatory Add a checklist of things that are required to be reviewed in order to have the PR approved List here all the items you have verified BEFORE sending this PR. Please DO NOT remove any item, striking through those that do not apply. (Just in case, strikethrough uses two tildes. Scratch this.) --> [ ] My code follows the style guidelines of this project [ ] I have commented my code, particularly in hard-to-understand areas [ ] I have made corresponding changes to the documentation [ ] I have made corresponding change to the default configuration files [ ] I have added tests that prove my fix is effective or that my feature works [ ] I have added an entry in `CHANGELOG.next.asciidoc` or `CHANGELOG-developer.next.asciidoc`. <!-- Will the changes introduced by this PR cause disruption to users in any way? If so, please describe what changes users could make on their end to nullify or minimize this disruption. Consider impacts in related systems, not just directly when using Beats. --> <!-- Recommended Add a checklist of things that are required to be reviewed in order to have the PR approved --> [ ] <!-- Recommended Explain here how this PR will be tested by the reviewer: commands, dependencies, steps, etc. --> <!-- Recommended Link related issues below. Insert the issue link or reference after the word "Closes" if merging this should automatically close it. Closes #123 Relates #123 Requires #123 Superseds #123 --> <!-- Recommended Explain here the different behaviors that this PR introduces or modifies in this project, user roles, environment configuration, etc. If you are familiar with Gherkin test scenarios, we recommend its usage: https://cucumber.io/docs/gherkin/reference/ --> <!-- Optional Add here screenshots about how the project will be changed after the PR is applied. They could be related to web pages, terminal, etc, or any other image you consider important to be shared with the team. --> <!-- Recommended Paste here output logs discovered while creating this PR, such as stack traces or integration logs, or any other output you consider important to be shared with the team. -->