Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: initial version #2

Merged
merged 1 commit into from
Oct 21, 2023
Merged

feat: initial version #2

merged 1 commit into from
Oct 21, 2023

Conversation

ReenigneArcher
Copy link
Member

Description

Initial version.

Screenshot

Issues Fixed or Closed

Type of Change

  • 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 not work as expected)
  • Dependency update (updates to dependencies)
  • Documentation update (changes to documentation)
  • Repository update (changes to repository files, e.g. .github/...)

Checklist

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have added or updated the in code docstring/documentation-blocks for new or existing methods/components

Branch Updates

LizardByte requires that branches be up-to-date before merging. This means that after any PR is merged, this branch
must be updated before it can be merged. You must also
Allow edits from maintainers.

  • I want maintainers to keep my branch updated

@ReenigneArcher ReenigneArcher force-pushed the feat-initial-version branch 10 times, most recently from 9017163 to 8a9e0de Compare October 21, 2023 02:20
@ReenigneArcher ReenigneArcher marked this pull request as ready for review October 21, 2023 02:30
@ReenigneArcher ReenigneArcher merged commit 35734a9 into master Oct 21, 2023
10 checks passed
@ReenigneArcher ReenigneArcher deleted the feat-initial-version branch October 21, 2023 02:30
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