Skip to content

Update package to onelitefeather#19

Merged
Joltras merged 1 commit into
masterfrom
feature/packageRename
Jul 9, 2025
Merged

Update package to onelitefeather#19
Joltras merged 1 commit into
masterfrom
feature/packageRename

Conversation

@theEvilReaper
Copy link
Copy Markdown
Contributor

Proposed changes

Currently, the project uses a mix of two different package naming conventions.
This pull request standardizes the naming by using only onelitefeather throughout the project.

Types of changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

  • Bugfix (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 not work as expected)
  • Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

  • I have read the CONTRIBUTING.md
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if appropriate)

@Joltras Joltras force-pushed the feature/packageRename branch from 2ec2418 to e4df2b4 Compare July 9, 2025 09:10
Copy link
Copy Markdown
Collaborator

@Joltras Joltras left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@Joltras Joltras merged commit 239a54a into master Jul 9, 2025
4 checks passed
@Joltras Joltras deleted the feature/packageRename branch July 9, 2025 09:16
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.

3 participants