Revert "ci: 🧪 Update cron schedule for weekly poetry bot to run every hour"

[Anselmoo]

This reverts commit 1e6758a.

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

Revert the cron schedule change for the weekly poetry bot to its original setting, running every Sunday at midnight instead of every hour.

CI:

• Revert the cron schedule for the weekly poetry bot to run every Sunday at midnight instead of every hour.

[semanticdiff-com]

Review changes with SemanticDiff.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request reverts a previous change to the cron schedule for the weekly poetry bot. It changes the schedule back from running every hour to running once a week on Sundays at midnight.

File-Level Changes

Change	Details	Files
Reverted the cron schedule for the weekly poetry bot	Removed the hourly cron schedule Restored the weekly cron schedule (Sundays at midnight) Uncommented the original cron schedule line	.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.

[sourcery-ai]

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

Overall Comments:

• Could you please provide a brief explanation of why this revert was necessary? A sentence or two about why the hourly schedule didn't work out would be helpful for future reference.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 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.}

[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

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (09115b5) to head (e41ad8c).
Report is 3 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #1518   +/-   ##
=========================================
  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.