Skip to content

Commit

Permalink
Update line endings given new .gitattributes, add PR changes to CHANG…
Browse files Browse the repository at this point in the history
…ELOG
  • Loading branch information
StephanieKemna committed Jul 25, 2024
1 parent 2ed1d1b commit 91e0be6
Show file tree
Hide file tree
Showing 9 changed files with 669 additions and 669 deletions.
96 changes: 48 additions & 48 deletions .github/pull_request_template.md
Original file line number Diff line number Diff line change
@@ -1,48 +1,48 @@
## Description

<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
<!--- Example: Resolves #15 -->
Resolves #issue_nr

<!-- A brief summary of the change and which issue is fixed. -->
<!-- What is the current behavior (pre-fix) and what is the new expected behavior? -->
...

<!-- List any dependencies that are required for this change (if any) -->

## How Has This Been Tested?

<!-- Describe the tests that you ran to verify your changes.-->
<!-- List any relevant details for your test configuration.-->

- [ ] Test A
- [ ] Test B

## Screenshots (if appropriate)

## Developer Checklist (before requesting PR review)

- [ ] My code follows the style guidelines of this project
- [ ] My changes generate no new warnings
- [ ] Any dependent changes have been merged and published in downstream modules

I have:

- [ ] commented my code, particularly in hard-to-understand areas
- [ ] performed a self-review of my own code
- [ ] not committed unnecessary formatting changes, thereby occluding the actual changes (e.g. change of tab spacing, eol, etc.)
- [ ] made corresponding changes to the documentation
- [ ] added change to CHANGELOG.md
- [ ] added tests that prove my fix is effective or that my feature works (for core features)

## Reviewer checklist

I have:

- [ ] performed a self-review of my own code have performed a review of the code
- [ ] tested that the software still works as expected
- [ ] checked updates to documentation
- [ ] checked that the CHANGELOG is updated
## Description

<!--- This project only accepts pull requests related to open issues -->
<!--- If suggesting a new feature or change, please discuss it in an issue first -->
<!--- If fixing a bug, there should be an issue describing it with steps to reproduce -->
<!--- Please link to the issue here: -->
<!--- Example: Resolves #15 -->
Resolves #issue_nr

<!-- A brief summary of the change and which issue is fixed. -->
<!-- What is the current behavior (pre-fix) and what is the new expected behavior? -->
...

<!-- List any dependencies that are required for this change (if any) -->

## How Has This Been Tested?

<!-- Describe the tests that you ran to verify your changes.-->
<!-- List any relevant details for your test configuration.-->

- [ ] Test A
- [ ] Test B

## Screenshots (if appropriate)

## Developer Checklist (before requesting PR review)

- [ ] My code follows the style guidelines of this project
- [ ] My changes generate no new warnings
- [ ] Any dependent changes have been merged and published in downstream modules

I have:

- [ ] commented my code, particularly in hard-to-understand areas
- [ ] performed a self-review of my own code
- [ ] not committed unnecessary formatting changes, thereby occluding the actual changes (e.g. change of tab spacing, eol, etc.)
- [ ] made corresponding changes to the documentation
- [ ] added change to CHANGELOG.md
- [ ] added tests that prove my fix is effective or that my feature works (for core features)

## Reviewer checklist

I have:

- [ ] performed a self-review of my own code have performed a review of the code
- [ ] tested that the software still works as expected
- [ ] checked updates to documentation
- [ ] checked that the CHANGELOG is updated
Loading

0 comments on commit 91e0be6

Please sign in to comment.