add appointment date to message

[sibalzer]

No description provided.

[codecov-commenter]

Codecov Report

Merging #113 (316de48) into main (179b62a) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #113      +/-   ##
==========================================
+ Coverage   92.07%   92.11%   +0.03%     
==========================================
  Files          12       12              
  Lines         606      609       +3     
==========================================
+ Hits          558      561       +3     
  Misses         48       48              

Impacted Files	Coverage Δ
tests/test_impfbot.py	100.00% <ø> (ø)
src/impfbot.py	87.50% <100.00%> (+1.01%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 179b62a...316de48. Read the comment docs.

oversight

[paulypeter]

I looked into a more permanent solution, but didn't find one I liked.. I guess this one is fine for a while

[sibalzer]

yea same, but we just need the date so it makes no difference if we get dd.mm.YYYY 01:00 during winter.

[paulypeter]

You're right, perfect

[paulypeter]

@sibalzer What would I have to do to merge this and release it as v3.1.0?

[sibalzer]

i'll use the google release please action with semantic commit/merge messages:

• fix: which represents bug fixes, and correlates to a SemVer patch.
• feat: which represents a new feature, and correlates to a SemVer minor.
• feat!:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a SemVer major.

this triggers the release please which creates a version pr and when i merge this the action creates a tag and deploys a new version