Testing for assignment on PR

[shinymack]

1. First, I will test the assignment command using the original issue_assign.py from the main branch.
2. Then, I will modify issue_assign.py on main.
3. Finally, I will test the assignment command again to check if the change worked.

[issue-assign-bot-shinymack]

Thank you for contributing to aeon

I did not find any labels to add based on the title. Please add the [ENH], [MNT], [BUG], [DOC], [REF], [DEP] and/or [GOV] tags to your pull requests titles. For now you can add the labels manually.

The Checks tab will show the status of our automated tests. You can click on individual test runs in the tab or "Details" in the panel below to see more information if there is a failure.

If our pre-commit code quality check fails, any trivial fixes will automatically be pushed to your PR unless it is a draft.

Don't hesitate to ask questions on the aeon Slack channel if you have any.

PR CI actions

These checkboxes will add labels to enable/disable CI functionality for this PR. This may not take effect immediately, and a new commit may be required to run the new configuration.

• Run pre-commit checks for all files
• Run mypy typecheck tests
• Run all pytest tests and configurations
• Run all notebook example tests
• Run numba-disabled codecov tests
• Stop automatic pre-commit fixes (always disabled for drafts)
• Disable numba cache loading
• Push an empty commit to re-run CI checks

[shinymack]

@aeon-actions-bot assign @shinymack

[shinymack]

Now checking after changing the issue_assign.py in main branch

[shinymack]

@aeon-actions-bot assign @shinymack