Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Changed the issue and pull request templates templates [#605]
* Updated the PR template. * Updated CONTRIBUTING.md to call out single commits. * Added a security issue template.
- Loading branch information
Showing
5 changed files
with
70 additions
and
61 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
--- | ||
name: Security issue | ||
about: Create a report to help us improve | ||
title: '[CVE-####-#####] Describe the security using a single sentence' | ||
labels: 'security' | ||
assignees: '' | ||
|
||
--- | ||
|
||
**NOTE: If this involves a pre-release version of ComiXed and not a release, then please send an email to the mailing list rather than creating an issue here. All such bug reports will be closed.** | ||
|
||
**Describe The Security Issue** | ||
A clear and concise description of what the issue is. Please include any links to the vulnerability and any affected dependencies. | ||
|
||
**Additional Context** | ||
Add any other context about the problem here. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,42 +1,27 @@ | ||
## Status | ||
**READY/IN DEVELOPMENT/HOLD** | ||
|
||
## Migrations | ||
YES | NO | ||
|
||
## Description | ||
A few sentences describing the overall goals of the pull request's commits. | ||
|
||
## Related PRs | ||
List related PRs against other branches: | ||
|
||
branch | PR | ||
------ | ------ | ||
other_pr_production | [link]() | ||
other_pr_master | [link]() | ||
## Changes Need To Be Discussed First | ||
|
||
Before opening a pull request, please be sure to announce your changes in [the | ||
developer mailing list](https://www.freelists.org/list/comixed-dev) (and subscribe if you | ||
haven't already). This will help speed up getting your pull request reviewed and merged. | ||
|
||
## Todos | ||
- [ ] Tests | ||
- [ ] Documentation | ||
**NOTE:** You can erase any parts of this template that are not applicable to your PR, | ||
including this top section. | ||
|
||
## Status | ||
READY/IN DEVELOPMENT/HOLD | ||
|
||
## Deploy Notes | ||
Notes regarding deployment the contained body of work. These should note any | ||
db migrations, etc. | ||
|
||
## Steps to Test or Reproduce | ||
Outline the steps to test or reproduce the PR here. | ||
|
||
```sh | ||
git pull --prune | ||
git checkout <feature_branch> | ||
bundle; script/server | ||
``` | ||
|
||
1. | ||
## Does this PR contain migrations? | ||
YES | NO | ||
|
||
## Impacted Areas in Application | ||
List general components of the application that this PR will affect: | ||
## Before You Submit Your PR: | ||
- [ ] Have you announced your PR on the comixed-dev mailing list? | ||
- [ ] Bug fix (non-breaking change which fixes an issue) | ||
- [ ] New feature (non-breaking change which adds functionality) | ||
- [ ] Breaking change (fix or feature that would cause existing functionality to change) | ||
- [ ] My code follows the code style of this project. | ||
- [ ] My change requires a change to the documentation. | ||
- [ ] I have updated the documentation accordingly. | ||
- [ ] I have read the **CONTRIBUTING** document. | ||
- [ ] I have added tests to cover my changes. | ||
- [ ] All new and existing tests passed. | ||
|
||
* |