Skip to content

Conversation

@0xEmma
Copy link
Collaborator

@0xEmma 0xEmma commented Oct 30, 2025

Types of changes

What types of changes does your code introduce?
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 not to work as expected).
  • Documentation Update (if none of the other choices applies).

Proposed changes

Describe your changes here and explain why we should accept this pull request. If it fixes a bug or resolves a feature
request, be sure to link to that issue.

Checklist

Put an x in the boxes that apply.

  • I have read and followed the CONTRIBUTING.md
    doc.
  • Lint and unit tests pass locally with my changes.
  • I have added the necessary documentation (if appropriate).

Additional context

Add any other context or screenshots here.

@codecov
Copy link

codecov bot commented Oct 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.24%. Comparing base (f05b789) to head (5fa766f).
⚠️ Report is 21 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #163      +/-   ##
==========================================
+ Coverage   58.91%   59.24%   +0.32%     
==========================================
  Files          50       50              
  Lines        2865     2905      +40     
==========================================
+ Hits         1688     1721      +33     
- Misses       1177     1184       +7     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.


def setup(bot: Bot) -> None:
"""Load the `MessageHandler` cog."""
# bot.add_cog(MessageHandler(bot))
Copy link
Contributor

Choose a reason for hiding this comment

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

The cog is disabled, should that be enabled?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Did not realize that; i was just wanting to hook into the on_message event and this made sense given the cogs pre-existing function

Copy link
Contributor

Choose a reason for hiding this comment

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

I'd recommend to:

  1. Uncomment bot.add_cog(MessageHandler(bot)) in the setup() function
  2. Optionally clean up the unused process_reverification code (since it just raises an error and creates noise in logs)

Copy link
Contributor

Choose a reason for hiding this comment

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

bump ☝️ @0xEmma

- Fix "In-order" typo to "In order" in welcome message
- Add test coverage for on_message welcome feature in auto_verify
- Fix broken assertion in test_ban.py (called_once_with -> assert_called_once_with)
@dimoschi dimoschi self-requested a review December 19, 2025 12:22
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