fix action flow

[KommuSoft]

fix action flow

Summary by CodeRabbit

• Tests

  • Expanded coverage for membership type checking, asserting errors on invalid tuple inputs.
  • Reformatted a couple of date-difference assertions without changing behavior.

• Chores

  • Streamlined CI by removing a redundant linter step from the formatting job.

• Style

  • Improved readability by reformatting an internal dictionary comprehension; no functional changes.

[coderabbitai]

Walkthrough

Removes a pylint step from the Black CI job, adds a test asserting TypeError for invalid membership input in timetest.py, reformats two assertions for readability, and reflows a dictionary comprehension in unit_of_time/init.py without changing behavior.

Changes

Cohort / File(s)	Summary of Changes
CI workflow tweak .github/workflows/build.yml	Removed standalone pylint step from the black job; other jobs and steps unchanged.
Test update and formatting timetest.py	Added membership test expecting TypeError for tuple input; reformatted two timedelta equality assertions to multi-line.
Code style reflow unit_of_time/__init__.py	Reflowed a dict comprehension in TimeunitKindMeta.unit_register to multi-line; semantics unchanged.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• pre-release #7 — Also edits .github/workflows/build.yml, particularly around adding the black job; related via the same workflow area.
• pylint matrix #11 — Adjusts CI linting in .github/workflows/build.yml by centralizing/adding a pylint job and Python matrix; related to the removed pylint step here.

Poem

I thump my paw at CI night,
One lint hops out of Black’s sight.
Tests now sniff tuples, “TypeError!” they cheer,
Dates align—one day, crystal clear.
In code burrows, lines realign,
A tidy warren—ship it fine. 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between cda9b9f and 051ef9c.

📒 Files selected for processing (3)

• .github/workflows/build.yml (0 hunks)
• timetest.py (2 hunks)
• unit_of_time/__init__.py (1 hunks)

💤 Files with no reviewable changes (1)

• .github/workflows/build.yml

🧰 Additional context used

🧬 Code graph analysis (1)

timetest.py (1)

unit_of_time/__init__.py (4)

• next (331-332)
• first_date (269-270)
• last_date (273-274)
• previous (265-266)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (5)

• GitHub Check: run tests (3.11)
• GitHub Check: run tests (3.13)
• GitHub Check: run tests (3.10)
• GitHub Check: run tests (3.9)
• GitHub Check: run tests (3.12)

🔇 Additional comments (3)

unit_of_time/__init__.py (1)

39-41: Reflow-only change improves readability; semantics unchanged. LGTM.

timetest.py (2)

113-114: Good: enforce TypeError on invalid membership tuple.
Matches Timeunit._get_range contract; prevents silent False on bad inputs.

---

156-161: Readability improvement for boundary-delta assertions.
Multi-line form is clearer; behavior unchanged. LGTM.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch issue/coverage-threshold

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.