suricata/.github/PULL_REQUEST_TEMPLATE.md

Make sure these boxes are checked accordingly before submitting your Pull Request -- thank you.

## Contribution style:
- [ ] I have read the contributing guide lines at
   https://docs.suricata.io/en/latest/devguide/contributing/contribution-process.html

## Our Contribution agreements:
- [ ] I have signed the Open Information Security Foundation contribution agreement at
   https://suricata.io/about/contribution-agreement/ (note: this is only required once)

## Changes (if applicable):
- [ ] I have updated the User Guide (in [doc/userguide/](https://github.com/OISF/suricata/tree/304271e63a9e388412f25f0f94a1a0da4bf619d9/doc/userguide)) to reflect the changes made
- [ ] I have updated the JSON schema (in [etc/schema.json](https://github.com/OISF/suricata/blob/304271e63a9e388412f25f0f94a1a0da4bf619d9/etc/schema.json)) to reflect all logging changes
      (including schema descriptions)
- [ ] I have created a ticket at
      https://redmine.openinfosecfoundation.org/projects/suricata/issues

Link to ticket: https://redmine.openinfosecfoundation.org/issues/

Describe changes:
-
-
-

### Provide values to any of the below to override the defaults.

- To use an LibHTP, Suricata-Verify or Suricata-Update pull request,
  link to the pull request in the respective `_BRANCH` variable.
- Leave unused overrides blank or remove.

SV_REPO=
SV_BRANCH=
SU_REPO=
SU_BRANCH=
LIBHTP_REPO=
LIBHTP_BRANCH=
github/pr-template: update contribution checks We have different types of checks, all in a single list. Adding a title of sorts to each group in the hopes of highlighting their purposes. When we add new items to the json schema, many times we don't add their descriptions, while this would be the perfect time to also do that. 6 months ago			`Make sure these boxes are checked accordingly before submitting your Pull Request -- thank you.`
github: add pull request template 8 years ago
github/pr-template: update contribution checks We have different types of checks, all in a single list. Adding a title of sorts to each group in the hopes of highlighting their purposes. When we add new items to the json schema, many times we don't add their descriptions, while this would be the perfect time to also do that. 6 months ago			`## Contribution style:`
github: improve template CLA request info Indicate that the CLA only has to be signed once, as we have had contributors think that was required for each new PR. 1 year ago			`- [ ] I have read the contributing guide lines at`
devguide: make 'contributing' a chapter This could be justified from a semantic point of view, and also can help in bringing more attention to where this information is, as it is less hidden, now. Also add Dev Guide as one of our resources in our Readme. 1 year ago			`https://docs.suricata.io/en/latest/devguide/contributing/contribution-process.html`
github/pr-template: update contribution checks We have different types of checks, all in a single list. Adding a title of sorts to each group in the hopes of highlighting their purposes. When we add new items to the json schema, many times we don't add their descriptions, while this would be the perfect time to also do that. 6 months ago
			`## Our Contribution agreements:`
github: improve template CLA request info Indicate that the CLA only has to be signed once, as we have had contributors think that was required for each new PR. 1 year ago			`- [ ] I have signed the Open Information Security Foundation contribution agreement at`
			`https://suricata.io/about/contribution-agreement/ (note: this is only required once)`
github/pr-template: update contribution checks We have different types of checks, all in a single list. Adding a title of sorts to each group in the hopes of highlighting their purposes. When we add new items to the json schema, many times we don't add their descriptions, while this would be the perfect time to also do that. 6 months ago
			`## Changes (if applicable):`
			`- [ ] I have updated the User Guide (in [doc/userguide/](https://github.com/OISF/suricata/tree/304271e63a9e388412f25f0f94a1a0da4bf619d9/doc/userguide)) to reflect the changes made`
			`- [ ] I have updated the JSON schema (in [etc/schema.json](https://github.com/OISF/suricata/blob/304271e63a9e388412f25f0f94a1a0da4bf619d9/etc/schema.json)) to reflect all logging changes`
			`(including schema descriptions)`
github: update pull request template Update the pull request template to suggest providing a link to the SV/LIBHTP pull request as this aides in cross linking. Also change the way to provide the link to the Redmine ticket, as it often results in linking to our Redmine, and add a checkbox for the creation of a ticket. 10 months ago			`- [ ] I have created a ticket at`
			`https://redmine.openinfosecfoundation.org/projects/suricata/issues`
github: add pull request template 8 years ago
github: update pull request template Update the pull request template to suggest providing a link to the SV/LIBHTP pull request as this aides in cross linking. Also change the way to provide the link to the Redmine ticket, as it often results in linking to our Redmine, and add a checkbox for the creation of a ticket. 10 months ago			`Link to ticket: https://redmine.openinfosecfoundation.org/issues/`
github: add pull request template 8 years ago
			`Describe changes:`
			`-`
			`-`
			`-`

github-ci: use bundle.sh script for libhtp, suricata-update Update the GitHub CI workflow to use the bundle.sh script to pull in Suricata-Update and libhtp. This means one less place where defaults are hardcoded and can get out of sync. This also simplifies the variable names that can be embedded in a pull request message to use the same variable names that bundle.sh expects. Of note, this removes the _PR variant, instead a branch name of "pr/N" can be used to specify a PR. 2 years ago			`### Provide values to any of the below to override the defaults.`

github: update pull request template Update the pull request template to suggest providing a link to the SV/LIBHTP pull request as this aides in cross linking. Also change the way to provide the link to the Redmine ticket, as it often results in linking to our Redmine, and add a checkbox for the creation of a ticket. 10 months ago			`- To use an LibHTP, Suricata-Verify or Suricata-Update pull request,`
			link to the pull request in the respective `_BRANCH` variable.
			`- Leave unused overrides blank or remove.`
github-ci: allow pull request URL in SV_BRANCH Allow the SV_BRANCH variable to contain the full link to an OISF/suricata-verify pull request. This will cause GitHub to create a cross-link for us. 2 years ago
github-ci: use bundle.sh script for libhtp, suricata-update Update the GitHub CI workflow to use the bundle.sh script to pull in Suricata-Update and libhtp. This means one less place where defaults are hardcoded and can get out of sync. This also simplifies the variable names that can be embedded in a pull request message to use the same variable names that bundle.sh expects. Of note, this removes the _PR variant, instead a branch name of "pr/N" can be used to specify a PR. 2 years ago			`SV_REPO=`
			`SV_BRANCH=`
			`SU_REPO=`
			`SU_BRANCH=`
			`LIBHTP_REPO=`
			`LIBHTP_BRANCH=`