test: verify auto-close workflow (PR should auto-close)

[bdraco]

Test PR to verify the workflow added in #477. This PR is opened from bdraco:master (a fork's default branch) and should be auto-closed by the workflow with a friendly comment.

Will be reverted on bdraco/master after the test.

[github-actions]

Hi @bdraco, thanks for opening a pull request! 🎉

It looks like this PR was opened from the master branch of your fork (bdraco/pySwitchbot), which is the same name as this repository's default branch. Working directly on master in your fork causes a few problems:

• Your fork's master branch will permanently diverge from sblibs/pySwitchbot:master, making it hard to keep your fork up to date.
• Any additional commits you push to master will be added to this PR, so you can't easily work on multiple changes at once.
• Pushing maintainer fixes to your branch is awkward, since it means committing directly to your fork's default branch.
• It makes local collaboration painful — master in a checkout becomes ambiguous between upstream and your fork, and maintainers end up with naming collisions when fetching your branch.

Please re-open this as a new PR from a dedicated feature branch. The usual flow looks like:

# Make sure your fork's master is up to date with upstream
git remote add upstream https://github.com/sblibs/pySwitchbot.git  # if you haven't already
git fetch upstream
git checkout master
git reset --hard upstream/master
git push --force-with-lease origin master

# Create a new branch for your change and cherry-pick / re-apply your commits there
git checkout -b my-feature-branch upstream/master
# ...re-apply your changes, then:
git push origin my-feature-branch

Then open a new pull request from my-feature-branch into sblibs/pySwitchbot:master.

Closing this PR for now — sorry for the friction, and thanks again for contributing! ❤️

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.