Skip to content

fix: complex typos#31

Merged
vEnhance merged 1 commit intovEnhance:mainfrom
Hiii-88888888:patch-1
Mar 21, 2026
Merged

fix: complex typos#31
vEnhance merged 1 commit intovEnhance:mainfrom
Hiii-88888888:patch-1

Conversation

@Hiii-88888888
Copy link
Copy Markdown
Contributor

No description provided.

@github-actions
Copy link
Copy Markdown

Hey there and thank you for opening this pull request! 👋

We require pull request titles to follow the Conventional Commits specification. This comment indicates a fix is needed to repair this.

How do I fix this?

For most of you, this means that the PR title should say either

  • fix: [short description here] (if you are fixing an issue)
  • feat: [short description here] (if you are introducing a new feature)

depending on whether you are fixing an issue or doing something new, respectively. But some other types might be suitable too, see the list below:

  • build: build related
  • ci: work related to CI
  • chore: updating deps, etc.
  • docs: documentation changes
  • drop: deleting stuff or removing a feature
  • edit: minor changes that don't constitute a new feature
  • perf: performance improvements
  • polish: copy editing or cleanup that doesn't affect functionality
  • refactor: major rewriting or restructuring that doesn't fix bugs or affect functionality
  • revert: revert commits
  • style: code style changes
  • tests: unit testing, etc.

Please adjust the proposed title and this check will resolve automatically!

Detailed error message

No release type found in pull request title "Typo fix". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:

  • fix
  • feat
  • build
  • ci
  • chore
  • docs
  • drop
  • edit
  • perf
  • polish
  • refactor
  • revert
  • style
  • tests

@vEnhance vEnhance changed the title Typo fix fix: complex typos Mar 21, 2026
@vEnhance
Copy link
Copy Markdown
Owner

Thanks! If you would like to be in the acknow, let me know what name you prefer.

@vEnhance vEnhance merged commit 29d0805 into vEnhance:main Mar 21, 2026
2 of 3 checks passed
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.

2 participants