Name the forge and the maintainer contact #17

Merged
mph merged 1 commit from wip/contributing-and-developer into main 2026-09-12 17:13:12 +00:00
Owner

Two statements in the repository were not true after the move to the forge.

  1. CONTRIBUTING.md said that a pull request triggers a GitHub Actions workflow. The checks run on Forgejo Actions.
  2. The ConformanceTest table sent a breaking change to "the release notes". The repository records those in CHANGELOG.md.

The POM developer entry also still named a GitHub profile and carried no contact address. It now names the maintainer profile on the forge and the maintainer email:

<developer>
    <id>mph</id>
    <name>Michal Příhoda</name>
    <url>https://code.iterative.works/mph</url>
    <email>michal@prihoda.net</email>
</developer>

Verification:

  • ./mill show webawesome.jvm.pomSettings and the generated POM both carry the new url and the email.
  • https://code.iterative.works/mph answers 200.
  • No line of build.mill exceeds the 100-column limit of .scalafmt.conf.

Scope: this affects 3.12.0.1-SNAPSHOT onward. The published 3.12.0 keeps the POM it has.

🤖 Generated with Claude Code

https://claude.ai/code/session_01B4W95VNg8J3zinj28YSSRE

Two statements in the repository were not true after the move to the forge. 1. `CONTRIBUTING.md` said that a pull request triggers a **GitHub Actions** workflow. The checks run on Forgejo Actions. 2. The `ConformanceTest` table sent a breaking change to "the release notes". The repository records those in `CHANGELOG.md`. The POM developer entry also still named a GitHub profile and carried no contact address. It now names the maintainer profile on the forge and the maintainer email: ```xml <developer> <id>mph</id> <name>Michal Příhoda</name> <url>https://code.iterative.works/mph</url> <email>michal@prihoda.net</email> </developer> ``` Verification: - `./mill show webawesome.jvm.pomSettings` and the generated POM both carry the new url and the email. - `https://code.iterative.works/mph` answers 200. - No line of build.mill exceeds the 100-column limit of .scalafmt.conf. Scope: this affects 3.12.0.1-SNAPSHOT onward. The published 3.12.0 keeps the POM it has. 🤖 Generated with [Claude Code](https://claude.com/claude-code) https://claude.ai/code/session_01B4W95VNg8J3zinj28YSSRE
Name the forge and the maintainer contact
All checks were successful
CI / format (pull_request) Successful in 43s
CI / compile (pull_request) Successful in 45s
CI / test (pull_request) Successful in 47s
CI / lint (pull_request) Successful in 52s
a173a79765
CONTRIBUTING said the check workflow runs on GitHub Actions. It runs on
Forgejo Actions. It also sent a breaking change to release notes, and the
repository records those in CHANGELOG.md.

The POM developer entry names the maintainer profile on the forge and
carries the maintainer email.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01B4W95VNg8J3zinj28YSSRE
mph merged commit 9cf79e066b into main 2026-09-12 17:13:12 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
iterative-works/scalatags-webawesome!17
No description provided.