Skip to content

Add licence to README - #53

Open
pandalump wants to merge 1 commit into
mainfrom
Add-licence-to-README
Open

Add licence to README#53
pandalump wants to merge 1 commit into
mainfrom
Add-licence-to-README

Conversation

@pandalump

@pandalump pandalump commented Jun 8, 2026

Copy link
Copy Markdown
Collaborator

Summary by Sourcery

Documentation:

  • Add a Licence section to the README specifying that Theoremc is distributed under the ISC licence.

@sourcery-ai

sourcery-ai Bot commented Jun 8, 2026

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Adds a licence section to the README documenting that Theoremc is distributed under the ISC licence.

File-Level Changes

Change Details Files
Document project licence in README
  • Append a new 'Licence' section to the README
  • State that Theoremc is distributed under the ISC licence and link to the official licence text
README.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

Note

Reviews paused

It looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the reviews.auto_review.auto_pause_after_reviewed_commits setting.

Use the following commands to manage reviews:

  • @coderabbitai resume to resume automatic reviews.
  • @coderabbitai review to trigger a single review.

Use the checkboxes below for quick actions:

  • ▶️ Resume reviews
  • 🔍 Trigger review

Add licence to README

Overview

This pull request adds a new "Licence" section to the README file, documenting that Theoremc is distributed under the ISC licence with a link to the licence text.

Changes

  • New "Licence" section added to README.md (+5 lines)

Impact

No changes to exported or public entities. This is a documentation-only update.

Walkthrough

The PR adds a "Licence" section to the README documenting that Theoremc is distributed under the ISC licence, including a hyperlink to the full licence text. This is a straightforward documentation update with minimal scope.

Changes

Licence Documentation

Layer / File(s) Summary
Licence section
README.md
A new Licence section is added to the README documenting ISC licence distribution with a hyperlink to the licence text.

Poem

📜 A licence emerges in five gentle lines,
ISC blessed, the code now defines,
Terms clear and linked for all to see,
Legal clarity for Theoremc.

🚥 Pre-merge checks | ✅ 20
✅ Passed checks (20 passed)
Check name Status Explanation
Title check ✅ Passed The pull request title clearly and directly describes the main change: adding a licence section to the README documentation.
Description check ✅ Passed The description is directly related to the changeset, accurately documenting the addition of a Licence section to the README specifying ISC licensing.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Testing (Overall) ✅ Passed Documentation amendments (licence notice in README) constitute neither new functionality nor behavioural changes; the testing requirement does not apply.
User-Facing Documentation ✅ Passed Adding a licence section to README.md is administrative metadata, not user-facing functionality or behaviour requiring documentation in users-guide.md per the custom check.
Developer Documentation ✅ Passed PR only adds a Licence section to README.md. No internal APIs, architectural, tooling, build, or design document changes requiring developer documentation updates.
Module-Level Documentation ✅ Passed All 76 new Rust modules (.rs files) in the PR carry module-level docstrings (//!) explaining their purpose, utility and function, fully satisfying the check requirements.
Testing (Unit And Behavioural) ✅ Passed PR adds README documentation only. Tests apply only to changes affecting external workflows, integration, persistence, CLI, network, UI, or system behaviour per check instructions.
Testing (Property / Proof) ✅ Passed The PR modifies only README.md to add a licence section, introducing no code, invariants, or proof assumptions that would warrant property tests or formal verification.
Testing (Compile-Time / Ui) ✅ Passed Documentation-only changes (README licence section) don't require compile-time or snapshot tests; the check applies to code introducing new behaviour or output.
Unit Architecture ✅ Passed This check applies to executable code architecture. The PR adds static documentation to README.md, which contains no code paths, dependencies, or architectural boundaries to assess.
Domain Architecture ✅ Passed PR modifies only README.md documentation. Domain Architecture check applies to code-level architectural boundaries, not documentation or project metadata.
Observability ✅ Passed Pull request adds only documentation to README.md, not operational code. Observability check is inapplicable as no operational behaviour is introduced or altered.
Security And Privacy ✅ Passed PR adds only documentation (ISC licence link to README); no secrets, credentials, sensitive data, auth/authz changes, or privacy concerns introduced.
Performance And Resource Use ✅ Passed PR modifies only README.md, adding 5 lines of licence documentation. Performance checks do not apply to documentation-only changes.
Concurrency And State ✅ Passed Pull request modifies only README.md with a pure documentation change adding a Licence section. No source code, concurrency primitives, shared state, async code, or parallelism present.
Architectural Complexity And Maintainability ✅ Passed This PR only adds a licence section to README—no code, abstractions, dependencies, or architectural changes. The check does not apply to pure documentation updates.
Rust Compiler Lint Integrity ✅ Passed The custom check concerns Rust compiler lint integrity and dead-code suppression. This PR modifies only README.md with no Rust code changes, rendering the check inapplicable.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch Add-licence-to-README

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

Comment @coderabbitai help to get the list of available commands and usage tips.

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've found 1 issue, and left some high level feedback:

  • Consider aligning the spelling and casing of “Licence”/“license” with the rest of the project (e.g., LICENSE file name and existing docs) for consistency across the repository.
Prompt for AI Agents
Please address the comments from this code review:

## Overall Comments
- Consider aligning the spelling and casing of “Licence”/“license” with the rest of the project (e.g., LICENSE file name and existing docs) for consistency across the repository.

## Individual Comments

### Comment 1
<location path="README.md" line_range="50-53" />
<code_context>
 mangling, and IO logic live in `crates/theoremc-core`. The root `theoremc`
 crate re-exports both. Import paths from `theoremc` are unchanged.
+
+## Licence
+
+Theoremc is distributed under the
+[ISC licence](https://opensource.org/licenses/ISC). 
</code_context>
<issue_to_address>
**suggestion (typo):** Consider aligning "Licence/licence" spelling with the rest of the project (e.g., "License") for consistency.

Both "Licence" and "licence" are valid British English, but many projects (and files like LICENSE) use "License". Please check how this term is used elsewhere in the repo and standardize on a single spelling (including headings and link text).
</issue_to_address>

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

Comment thread README.md
Comment on lines +50 to +53
## Licence

Theoremc is distributed under the
[ISC licence](https://opensource.org/licenses/ISC).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

suggestion (typo): Consider aligning "Licence/licence" spelling with the rest of the project (e.g., "License") for consistency.

Both "Licence" and "licence" are valid British English, but many projects (and files like LICENSE) use "License". Please check how this term is used elsewhere in the repo and standardize on a single spelling (including headings and link text).

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@README.md`:
- Line 53: Remove the trailing space at the end of the "[ISC
licence](https://opensource.org/licenses/ISC)" line in README.md so the line
ends with the closing parenthesis (no trailing whitespace), fixing the MD009
markdownlint failure and unblocking CI.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 9e48b4d9-21e9-4883-a242-809ff49fbc7e

📥 Commits

Reviewing files that changed from the base of the PR and between 8f48abb and 2d6b94a.

📒 Files selected for processing (1)
  • README.md

Comment thread README.md
## Licence

Theoremc is distributed under the
[ISC licence](https://opensource.org/licenses/ISC).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Remove trailing whitespace on Line 53 to unblock CI.

Delete the single trailing space at the end of the licence link line; the
current content fails markdownlint (MD009) and breaks the CI quality gate.

Triage: [type:syntax/md]

Patch
-Theoremc is distributed under the
-[ISC licence](https://opensource.org/licenses/ISC). 
+Theoremc is distributed under the
+[ISC licence](https://opensource.org/licenses/ISC).

As per coding guidelines, "**/*.md: Markdown paragraphs and bullet points
must be wrapped at 80 columns" and markdown syntax/lint requirements must be
followed, including valid whitespace handling.

🧰 Tools
🪛 GitHub Actions: CI / 0_build-test.txt

[error] 53-53: markdownlint-cli2/markdownlint MD009/no-trailing-spaces: Trailing spaces [Expected: 0 or 2; Actual: 1]

🪛 GitHub Actions: CI / build-test

[error] 53-53: markdownlint-cli2 (markdownlint v0.38.0) failed: MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1].

🪛 GitHub Check: build-test

[failure] 53-53: Trailing spaces
README.md:53:52 MD009/no-trailing-spaces Trailing spaces [Expected: 0 or 2; Actual: 1] https://github.com/DavidAnson/markdownlint/blob/v0.38.0/doc/md009.md

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@README.md` at line 53, Remove the trailing space at the end of the "[ISC
licence](https://opensource.org/licenses/ISC)" line in README.md so the line
ends with the closing parenthesis (no trailing whitespace), fixing the MD009
markdownlint failure and unblocking CI.

Sources: Coding guidelines, Linters/SAST tools, Pipeline failures

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant