suricata/.github/PULL_REQUEST_TEMPLATE.md

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

- [ ] I have read the contributing guide lines at
   https://docs.suricata.io/en/latest/devguide/contributing/contribution-process.html
- [ ] I have signed the Open Information Security Foundation contribution agreement at
   https://suricata.io/about/contribution-agreement/ (note: this is only required once)
- [ ] I have updated the user guide (in doc/userguide/) to reflect the changes made (if applicable)

Link to [redmine](https://redmine.openinfosecfoundation.org/projects/suricata/issues) ticket:

Describe changes:
-
-
-

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

To use a pull request use a branch name like `pr/N` where `N` is the
pull request number.

Alternatively, `SV_BRANCH` may also be a link to an
OISF/suricata-verify pull-request.

```
SV_REPO=
SV_BRANCH=
SU_REPO=
SU_BRANCH=
LIBHTP_REPO=
LIBHTP_BRANCH=
```
github: add pull request template 7 years ago			`Make sure these boxes are signed before submitting your Pull Request -- thank you.`

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. 12 months 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. 11 months ago			`https://docs.suricata.io/en/latest/devguide/contributing/contribution-process.html`
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. 12 months 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: add pull request template 7 years ago			`- [ ] I have updated the user guide (in doc/userguide/) to reflect the changes made (if applicable)`

			`Link to [redmine](https://redmine.openinfosecfoundation.org/projects/suricata/issues) ticket:`

			`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-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. 1 year ago			To use a pull request use a branch name like `pr/N` where `N` is the
			`pull request number.`

			Alternatively, `SV_BRANCH` may also be a link to an
			`OISF/suricata-verify pull-request.`
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=`
			```