• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

PyCalendar / icalendar / 43122188202
98%

Build:
DEFAULT BRANCH: main
Ran 11 Nov 2026 11:46PM UTC
Jobs 7
Files 324
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

11 Nov 2026 11:44PM UTC coverage: 97.991% (+0.005%) from 97.986%
43122188202

push

github

web-flow
Add vCalAddress.has_email for matching calendar users (#2057)

* Add vCalAddress.has_email for matching calendar users

Match the calendar address and EMAIL parameter case-insensitively, with an optional mailto: prefix. Document the method and cover parameter changes and calendar round trips.

AI assistance: OpenAI Codex (GPT-6) reviewed issue scope and overlapping PRs, drafted the method, documentation and tests, and ran validation. Prompt summary: Find and implement a fifth icalendar contribution building on the existing EMAIL parameter.

* Fix duplicate changelog fragment for has_email

Rename the new fragment to 1916.feature.1 so it does not collide with the existing 1916.feature.rst entry in Towncrier.

AI assistance: OpenAI Codex (GPT-6) helped diagnose the duplicate fragment, rename it, and validate the fix.

* Use casefold for has_email and clarify its docstring

Add Unicode matching tests for the calendar address and EMAIL parameter.
Mark the required parameter and document the return type.

OpenAI Codex assisted with these changes and validation.

* Remove misleading has_email docstring sentence

Apply the review suggestion to remove the claim that both addresses are
checked. Matching uses any(), which can stop after the first match.
No runtime behavior changes.

AI disclosure: I proposed the requirements and reviewed the changes before
submission. OpenAI Codex using GPT-6 Astra helped implement the changes
and run validation. The model identification is confirmed by me.

Prompt summary: address the review feedback on has_email, remove the
misleading docstring sentence, run the focused tests and code checks,
and prepare the changes for my review before submission.

For completeness, the AI assistance in earlier commits in this PR also
used GPT-6 Astra. It included investigating the issue, drafting the
implementation, documentation and tests, diagnosing the duplicate news
fragment, and running validation. For 37ac034a specifically, the reques... (continued)

2126 of 2280 branches covered (93.25%)

Branch coverage included in aggregate %.

52 of 52 new or added lines in 2 files covered. (100.0%)

19242 of 19526 relevant lines covered (98.55%)

6.89 hits per line

Jobs
ID Job ID Ran Files Coverage
1 run-pypy3 - 43122188202.1 12 Nov 2026 12:11AM UTC 324
97.96
GitHub Action Run
2 run-3.13 - 43122188202.2 11 Nov 2026 11:47PM UTC 324
97.96
GitHub Action Run
3 run-3.10 - 43122188202.3 11 Nov 2026 11:47PM UTC 324
97.97
GitHub Action Run
4 run-3.10 (nopytz) - 43122188202.4 11 Nov 2026 11:47PM UTC 324
97.97
GitHub Action Run
5 run-3.11 - 43122188202.5 11 Nov 2026 11:48PM UTC 324
97.96
GitHub Action Run
6 run-3.12 - 43122188202.6 11 Nov 2026 11:47PM UTC 324
97.96
GitHub Action Run
7 run-3.14 - 43122188202.7 11 Nov 2026 11:46PM UTC 324
97.96
GitHub Action Run
Source Files on build 43122188202
  • Tree
  • List 324
  • Changed 1
  • Source Changed 1
  • Coverage Changed 1
Coverage ∆ File Lines Relevant Covered Missed Hits/Line Branch Hits Branch Misses
  • Back to Repo
  • Github Actions Build #43122188202
  • 804ae06e on github
  • Prev Build on main (#43029622416)
  • Next Build on main (#43232712735)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc