Skip to content

Devel (#28)#29

Merged
SunDevil311 merged 1 commit intodevelfrom
master
Mar 15, 2025
Merged

Devel (#28)#29
SunDevil311 merged 1 commit intodevelfrom
master

Conversation

@SunDevil311
Copy link
Member

Types of changes

  • 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)

Checklist

  • 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 added tests to cover my changes.
  • All new and existing tests passed.

Pull requests should be thought of as a conversation. There will be some back and forth when trying to get code merged into this or any other project.

With all but the simplest changes you can and should expect that the maintainers of the project will request changes to your code.

Please be aware of that and check in after you open your PR in order to get your code merged in cleanly.

Thank you!

Types of changes

  • 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)

Checklist

  • 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.

Pull requests should be thought of as a conversation. There will be some back and forth when trying to get code merged into this or any other project.

With all but the simplest changes you can and should expect that the maintainers of the project will request changes to your code.

Please be aware of that and check in after you open your PR in order to get your code merged in cleanly.

Thank you!

## Types of changes

<!--- What types of changes does your code introduce? Put an `x` in all
the boxes that apply: -->

- [X] Bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to change)

## Checklist

<!--- Go over all the following points, and put an `x` in all the boxes
that apply. -->
<!--- If you're unsure about any of these, don't hesitate to ask. We're
here to help! -->

- [X] My code follows the code style of this project.
- [ ] My change requires a change to the documentation.
- [ ] I have updated the documentation accordingly.
- [X] I have added tests to cover my changes.
- [X] All new and existing tests passed.

Pull requests should be thought of as a conversation. There will be some
back and forth when trying to get code merged into this or any other
project.

With all but the simplest changes you can and should expect that the
maintainers of the project will request changes to your code.

Please be aware of that and check in after you open your PR in order to
get your code merged in cleanly.

Thank you!
@SunDevil311 SunDevil311 self-assigned this Mar 15, 2025
@SunDevil311 SunDevil311 merged commit 9a2d213 into devel Mar 15, 2025
9 checks passed
@SunDevil311 SunDevil311 mentioned this pull request Mar 15, 2025
SunDevil311 added a commit that referenced this pull request Mar 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant