Skip to content

Conversation

@ferreteleco
Copy link
Owner

Proposed changes

Fixes #10
Fixes #8

Types of changes

What types of changes does the PR introduce?

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Test coverage improvement (Adds new unit tests or improves existing ones)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

  • Introduced code follows the style guidelines of this project
  • Introduced code includes tests that prove fix is effective or feature works (if applicable)
  • Introduced code includes necessary documentation (if applicable)
  • Author has performed a self-review of the introduced code
  • Introduced code includes relevant comments, particularly in hard-to-understand areas
  • New and existing unit tests pass locally with changes included
  • Any dependent changes have been merged and published in downstream modules

How Has This Been Tested?

Test Configuration:

  • Cookiecutter version: 2.1.1
  • Python version: 3.11.2
  • OS Version: Windows 11

@ferreteleco ferreteleco merged commit 6a211bf into master Mar 17, 2023
@ferreteleco ferreteleco deleted the feature/release-actions branch March 17, 2023 01:48
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.

Add action to generate release on tag push Add action for building python artifact

2 participants