fix: 📄 Update GitHub Actions workflow to use 'gh pr merge' command

[Anselmoo]

All PR-Submissions:

---

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open
  Pull Requests for the same
  update/change?

New ✨✨ Feature-Submissions:

---

• Does your submission pass tests?
• Have you lint your code locally prior to submission? Fixed:
• This PR is for a new feature, not a bug fix.

Changes to ⚙️ Core-Features:

---

• Have you added an explanation of what your changes do and why you'd like
  us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully run tests with your changes locally?

Summary by Sourcery

Update the GitHub Actions workflow to enhance testing and authentication capabilities by allowing manual triggers, adjusting the cron schedule, and configuring authentication for pushing changes.

CI:

• Update GitHub Actions workflow to allow manual triggering with 'workflow_dispatch'.
• Modify the cron schedule to run every hour for testing purposes.
• Add 'gh auth setup-git' command and set 'GITHUB_TOKEN' environment variable for authentication in the workflow.

[semanticdiff-com]

Review changes with SemanticDiff.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the GitHub Actions workflow to use the 'gh pr merge' command and modifies the cron schedule for the weekly poetry update. It also adds a manual trigger option and improves the git push process.

File-Level Changes

Change	Details	Files
Modified cron schedule and added manual trigger	Changed cron schedule from every minute to every hour for testing purposes Added a commented-out cron schedule that runs every hour Added workflow_dispatch event to allow manual triggering of the workflow	.github/workflows/weekly-poetry-bot.yml
Updated git push process	Added 'gh auth setup-git' command before git push Added GITHUB_TOKEN environment variable for authentication	.github/workflows/weekly-poetry-bot.yml

---

Tips

• Trigger a new Sourcery review by commenting @sourcery-ai review on the pull request.
• Continue your discussion with Sourcery by replying directly to review comments.
• You can change your review settings at any time by accessing your dashboard:
  • Enable or disable the Sourcery-generated pull request summary or reviewer's guide;
  • Change the review language;
• You can always contact us if you have any questions or feedback.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sourcery-ai]

Hey @Anselmoo - I've reviewed your changes - here's some feedback:

Overall Comments:

• Clarify the cron schedule comments to accurately reflect the intended schedule.
• Consider adding a brief explanation in the PR description about the addition of 'gh auth setup-git' and the use of 'GITHUB_TOKEN'.

Here's what I looked at during the review

• 🟡 General issues: 1 issue found
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment to tell me if it was helpful.}

[sourcery-ai]

suggestion (performance): Consider using a weekly schedule for production

The current cron schedule runs every minute, which is excessive for a weekly update. For production, consider using the weekly schedule '0 0 * * 0' and remove the testing schedules to avoid unnecessary resource consumption and potential rate limiting issues.

Suggested change

	- cron: '* * * * *' # Runs every hour for testing purposes
	- cron: '0 0 * * 0' # Runs weekly on Sunday at midnight

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (c62063b) to head (8bd58ff).
Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1534   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           44        44           
  Lines         4466      4466           
=========================================
  Hits          4466      4466           

Flag	Coverage Δ
unittests	100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.