Skip to content

Conversation

Paillat-dev
Copy link
Member

@Paillat-dev Paillat-dev commented Mar 2, 2025

Summary

I was working on smth else when I stumbeld upon this, which is obviously wrong since rn it always evaulates to False.

Information

  • This PR fixes an issue.
  • This PR adds something new (e.g. new method or parameters).
  • This PR is a breaking change (e.g. methods or parameters removed/renamed).
  • This PR is not a code change (e.g. documentation, README, typehinting,
    examples, ...).

Checklist

  • I have searched the open pull requests for duplicates.
  • If code changes were made then they have been tested.
    • I have updated the documentation to reflect the changes.
  • If type: ignore comments were used, a comment is also left explaining why.
  • I have updated the changelog to include these changes.

@Paillat-dev
Copy link
Member Author

Does this even need changelog ?

@Lulalaby Lulalaby enabled auto-merge (squash) March 2, 2025 20:44
@Lulalaby Lulalaby merged commit ace28d8 into Pycord-Development:master Mar 2, 2025
28 checks passed
@Lulalaby
Copy link
Member

Lulalaby commented Mar 2, 2025

no

@Paillat-dev
Copy link
Member Author

ok

@Paillat-dev Paillat-dev deleted the fix/typo-is-in branch March 2, 2025 20:45
Paillat-dev added a commit to Paillat-dev/pycord that referenced this pull request Mar 2, 2025
🩹 Fix typo `is` instead of `in`
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