Skip to content

MPT-20094 reorganize repository documentation#299

Merged
d3rky merged 1 commit intomainfrom
feature/MPT-20094/generate-technical-documentation-for-the-repo
Apr 14, 2026
Merged

MPT-20094 reorganize repository documentation#299
d3rky merged 1 commit intomainfrom
feature/MPT-20094/generate-technical-documentation-for-the-repo

Conversation

@d3rky
Copy link
Copy Markdown
Contributor

@d3rky d3rky commented Apr 14, 2026

🤖 AI-generated PR — Please review carefully.

Summary

  • replace PROJECT_DESCRIPTION with a developer-facing usage guide for library consumers
  • reduce README to a concise entry point and align AGENTS/Copilot docs with the new structure
  • remove duplicated local documentation content, use safe placeholders in examples, and add a direct OpenAPI spec link

Testing

  • make check

Closes MPT-20094

Closes MPT-20094

Release Notes

  • New documentation structure: Replaced docs/PROJECT_DESCRIPTION.md with a new developer-focused docs/usage.md providing installation, configuration, and usage examples for synchronous and asynchronous client patterns.

  • README.md refocus: Simplified README to a concise entry point with a new Documentation section linking to key resources (AGENTS.md, usage guide, architecture, testing, contributing docs, and OpenAPI spec). Removed quality badges and usage code snippets.

  • AGENTS.md reorganization: Restructured with a "Documentation Reading Order" guide, expanded "Key Commands" table with Docker-based targets, and added "Repository Rules" section linking to shared standards from mpt-extension-skills. Updated API reference wording to reference "MPT OpenAPI spec."

  • AI agent configuration update: Updated .github/workflows/copilot-instructions.md from Python-specific coding conventions to a repository-wide instruction pointing to AGENTS.md.

  • Contributing guidance consolidation: Replaced local contribution content in docs/contributing.md with repository-specific guidance pointing to shared engineering standards. Added explicit "Development Model" using Docker and "Repository-Specific Expectations" for code changes.

  • Documentation standards definition: Added new docs/documentation.md defining repository documentation rules, specifying README.md as human entry point, AGENTS.md as AI entry point, and mandating use of shared standards from mpt-extension-skills instead of local copies.

  • Docker-centric local development: Refactored docs/local-development.md to emphasize Docker-only workflow with make bash and make run commands; simplified environment variables section with cross-references to usage.md and e2e_tests.md.

  • Testing documentation updates: Reorganized docs/testing.md to clarify test scopes, document Docker-based make command behavior, and define repository constraints for E2E testing and coverage expectations.

  • Build configuration updates: Updated pyproject.toml to reference README.md instead of docs/PROJECT_DESCRIPTION.md as project readme, with adjusted Hatch packaging includes for distributions.

@d3rky d3rky requested a review from a team as a code owner April 14, 2026 13:19
@d3rky d3rky requested review from alephsur and svazquezco April 14, 2026 13:19
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 14, 2026

📝 Walkthrough

Walkthrough

Restructures repository documentation and developer workflow toward a Docker-first model: replaces Python-specific Copilot guidance with a generic entry point, consolidates usage and docs into new docs/usage.md and docs/documentation.md, removes docs/PROJECT_DESCRIPTION.md, and updates README, AGENTS.md, contributing/local-development/testing docs, and packaging metadata.

Changes

Cohort / File(s) Summary
Copilot & Agent Guidance
.github/workflows/copilot-instructions.md, AGENTS.md
Replaced Python-scoped Copilot instructions with a repository-wide generic instruction pointing to ../../AGENTS.md; reorganized AGENTS.md reading order, added repository rules and new key commands (make bash, make run).
Top-level README & Removed Page
README.md, docs/PROJECT_DESCRIPTION.md
Removed three badges and the prior ## Usage section; added a ## Documentation section pointing to docs/usage.md and related docs; deleted docs/PROJECT_DESCRIPTION.md.
Documentation Index & Usage
docs/documentation.md, docs/usage.md
Added docs/documentation.md with documentation rules and a documentation map; added docs/usage.md with installation, env/config, sync/async client examples, resource list, and RQL usage.
Contribution & Local Dev
docs/contributing.md, docs/local-development.md
Replaced package-specific contributing guidance with references to shared standards (mpt-extension-skills); converted local development docs to Docker-first flow (make bash, make run) and simplified env/service explanations.
Testing
docs/testing.md
Refocused testing doc to repository-specific behavior: defined unit (tests/unit/) vs E2E (tests/e2e/) scopes, Docker make test targets mapping, pytest settings pointer, and coverage/constraint notes.
Packaging Metadata
pyproject.toml
Updated project readme metadata to README.md and adjusted hatch build includes to include README.md while removing docs/PROJECT_DESCRIPTION.md.
Repository Documentation Rules
docs/documentation.md, docs/contributing.md, docs/...
Centralized documentation rules, mandated linking to shared engineering rules, and added change/update guidance; no code or public API changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Single Commit Required ❓ Inconclusive Cannot determine the exact number of commits in this PR without access to remote branch information or GitHub API data showing the PR's commit history. Access git branch comparison (git rev-list --count origin/main..HEAD) or view the PR's Commits tab on GitHub to verify the actual commit count.
✅ Passed checks (2 passed)
Check name Status Explanation
Jira Issue Key In Title ✅ Passed The PR title contains exactly one Jira issue key (MPT-20094) in the correct format.
Test Coverage Required ✅ Passed PR modifies only documentation and configuration files with no code or test file changes in the package.

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


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

@d3rky d3rky force-pushed the feature/MPT-20094/generate-technical-documentation-for-the-repo branch from 325c719 to 7e9eded Compare April 14, 2026 13:23
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/contributing.md`:
- Around line 8-12: Update the links listed in docs/contributing.md to use the
repository’s canonical standards: replace the current Python, packages, pull
requests, documentation and Makefile links with the shared standards references
— specifically point to standards/contributing-standard.md,
standards/pull-request-guidelines.md, standards/python-style-guide.md, and
standards/testing-standard.md where applicable — so the contributor guidance
matches the repository baseline; ensure the list entries and link text reflect
these canonical filenames and remove or consolidate any redundant/non-canonical
links.

In `@docs/testing.md`:
- Around line 3-5: Update the broken shared-standard link in docs/testing.md by
replacing the reference to "standards/unittests.md" with the canonical
"standards/testing-standard.md"; locate the link text string
"standards/unittests.md" in docs/testing.md and update it so the sentence reads
and links to standards/testing-standard.md (ensure any surrounding Markdown
formatting and the existing sentence about repository-specific testing behavior
remain unchanged).
🪄 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: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 3875cb3e-eb72-41e3-8ddc-56fb1ebbe2b9

📥 Commits

Reviewing files that changed from the base of the PR and between 4092352 and 325c719.

📒 Files selected for processing (10)
  • .github/workflows/copilot-instructions.md
  • AGENTS.md
  • README.md
  • docs/PROJECT_DESCRIPTION.md
  • docs/contributing.md
  • docs/documentation.md
  • docs/local-development.md
  • docs/testing.md
  • docs/usage.md
  • pyproject.toml
💤 Files with no reviewable changes (1)
  • docs/PROJECT_DESCRIPTION.md

Comment thread docs/contributing.md
Comment thread docs/testing.md
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 2

♻️ Duplicate comments (1)
docs/contributing.md (1)

8-12: ⚠️ Potential issue | 🟡 Minor

Use the repository’s canonical shared-standard links.

These links still don’t match the standard pages this repo has established as the baseline for contributor guidance. Please align them to the canonical targets.

Suggested link updates
-- [Python coding conventions](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/python-coding.md)
-- [Packages and dependencies](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/packages-and-dependencies.md)
-- [Pull requests](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/pull-requests.md)
-- [Repository documentation](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/documentation.md)
-- [Makefile structure](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/makefiles.md)
+- [Contributing standard](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/contributing-standard.md)
+- [Pull request guidelines](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/pull-request-guidelines.md)
+- [Python style guide](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/python-style-guide.md)
+- [Testing standard](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/testing-standard.md)

Based on learnings: "Follow the pull request guidelines defined in standards/pull-request-guidelines.md ... Applies to **/.py: standards/python-style-guide.md ... Applies to **/test_.py: standards/testing-standard.md."

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/contributing.md` around lines 8 - 12, Replace the non-canonical links in
the contributing page that point to legacy files (e.g. python-coding.md,
packages-and-dependencies.md, pull-requests.md, documentation.md, makefiles.md)
with the repository’s canonical standard targets: use
standards/python-style-guide.md for Python conventions (and
standards/testing-standard.md for test files),
standards/pull-request-guidelines.md for PR guidance, and the appropriate
canonical standards pages for packages/dependencies, documentation, and Makefile
structure; update the link texts/URLs in the list so they reference those
canonical files.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/usage.md`:
- Around line 35-37: The sample .env entry uses a token-like value
(MPT_API_TOKEN=eyJhbGciOiJSUzI1NiIs...) which can trigger secret scanners;
replace that literal JWT-like string with a clear placeholder such as
MPT_API_TOKEN=<YOUR_API_TOKEN> or MPT_API_TOKEN=REPLACE_WITH_API_TOKEN and
optionally add a short comment showing format if needed (e.g., "# paste your API
token here"). Update the example line containing MPT_API_TOKEN and ensure other
env examples (e.g., MPT_API_BASE_URL) follow the same non-secret placeholder
approach.
- Around line 119-120: Update the sentence that references the "MPT OpenAPI
spec" so it includes a direct markdown link to the actual OpenAPI spec URL (or
internal spec file) alongside the existing architecture.md link; locate the
sentence "See [architecture.md](architecture.md) for the repository structure
and the MPT OpenAPI spec for the upstream endpoint contract." in docs/usage.md
and change the text so "MPT OpenAPI spec" is a clickable link pointing to the
spec (e.g., replace plain text with [MPT OpenAPI spec](<SPEC_URL_OR_PATH>)).

---

Duplicate comments:
In `@docs/contributing.md`:
- Around line 8-12: Replace the non-canonical links in the contributing page
that point to legacy files (e.g. python-coding.md, packages-and-dependencies.md,
pull-requests.md, documentation.md, makefiles.md) with the repository’s
canonical standard targets: use standards/python-style-guide.md for Python
conventions (and standards/testing-standard.md for test files),
standards/pull-request-guidelines.md for PR guidance, and the appropriate
canonical standards pages for packages/dependencies, documentation, and Makefile
structure; update the link texts/URLs in the list so they reference those
canonical files.
🪄 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: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: eeb31185-0d0f-44d0-851d-efc4de9d338c

📥 Commits

Reviewing files that changed from the base of the PR and between 325c719 and 7e9eded.

📒 Files selected for processing (10)
  • .github/workflows/copilot-instructions.md
  • AGENTS.md
  • README.md
  • docs/PROJECT_DESCRIPTION.md
  • docs/contributing.md
  • docs/documentation.md
  • docs/local-development.md
  • docs/testing.md
  • docs/usage.md
  • pyproject.toml
💤 Files with no reviewable changes (1)
  • docs/PROJECT_DESCRIPTION.md
✅ Files skipped from review due to trivial changes (2)
  • .github/workflows/copilot-instructions.md
  • docs/documentation.md
🚧 Files skipped from review as they are similar to previous changes (4)
  • pyproject.toml
  • docs/local-development.md
  • docs/testing.md
  • AGENTS.md

Comment thread docs/usage.md Outdated
Comment thread docs/usage.md Outdated
@d3rky d3rky force-pushed the feature/MPT-20094/generate-technical-documentation-for-the-repo branch from 7e9eded to 4238e8e Compare April 14, 2026 13:32
Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (1)
docs/contributing.md (1)

8-10: ⚠️ Potential issue | 🟡 Minor

Align shared-standard links with the repository’s canonical standard filenames.

The current targets (python-coding.md, pull-requests.md) still don’t match the canonical standards previously established for this repo (python-style-guide.md, pull-request-guidelines.md; plus include contributing-standard.md in this section).

Based on learnings: "Follow the contributing standards defined in standards/contributing-standard.md..." and "Follow the pull request guidelines defined in standards/pull-request-guidelines.md..." and "Applies to **/*.py: ... standards/python-style-guide.md".

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/contributing.md` around lines 8 - 10, Update the three links in the list
to point to the repo's canonical standard filenames: replace the
`python-coding.md` link with `python-style-guide.md`, replace `pull-requests.md`
with `pull-request-guidelines.md`, and add an entry for
`contributing-standard.md` (e.g., include a new bullet "Contributing standards"
linking to `standards/contributing-standard.md`) so the list contains:
python-style-guide.md, packages-and-dependencies.md (unchanged),
pull-request-guidelines.md, and contributing-standard.md; ensure the visible
link text matches the target filenames for clarity.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@pyproject.toml`:
- Line 56: The package include list currently only contains "mpt_api_client"
which excludes the README referenced by project.readme; update the build include
so README.md is packaged into both sdist and wheel by adding "README.md" (and
optionally other docs like "LICENSE") to the include list used for sdist/wheel
generation so that the sdist contains the README and wheel builds from sdist
succeed; specifically modify the include = ["mpt_api_client"] entry in
pyproject.toml to also include "README.md" (and any other necessary files).

---

Duplicate comments:
In `@docs/contributing.md`:
- Around line 8-10: Update the three links in the list to point to the repo's
canonical standard filenames: replace the `python-coding.md` link with
`python-style-guide.md`, replace `pull-requests.md` with
`pull-request-guidelines.md`, and add an entry for `contributing-standard.md`
(e.g., include a new bullet "Contributing standards" linking to
`standards/contributing-standard.md`) so the list contains:
python-style-guide.md, packages-and-dependencies.md (unchanged),
pull-request-guidelines.md, and contributing-standard.md; ensure the visible
link text matches the target filenames for clarity.
🪄 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: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: cb454008-8e27-40ad-92c6-d2dda167154f

📥 Commits

Reviewing files that changed from the base of the PR and between 7e9eded and 4238e8e.

📒 Files selected for processing (10)
  • .github/workflows/copilot-instructions.md
  • AGENTS.md
  • README.md
  • docs/PROJECT_DESCRIPTION.md
  • docs/contributing.md
  • docs/documentation.md
  • docs/local-development.md
  • docs/testing.md
  • docs/usage.md
  • pyproject.toml
💤 Files with no reviewable changes (1)
  • docs/PROJECT_DESCRIPTION.md
✅ Files skipped from review due to trivial changes (5)
  • .github/workflows/copilot-instructions.md
  • docs/testing.md
  • docs/documentation.md
  • README.md
  • docs/usage.md
🚧 Files skipped from review as they are similar to previous changes (2)
  • AGENTS.md
  • docs/local-development.md

Comment thread pyproject.toml Outdated
AI Generated.
Rework the repository documentation structure around a developer-focused usage guide, shared-standard links, and a concise README. Replace PROJECT_DESCRIPTION with usage.md, add documentation rules, and keep Docker-based workflow guidance in the topic-specific docs.
@d3rky d3rky force-pushed the feature/MPT-20094/generate-technical-documentation-for-the-repo branch from 4238e8e to 4a2fcbe Compare April 14, 2026 13:38
@sonarqubecloud
Copy link
Copy Markdown

Copy link
Copy Markdown

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

♻️ Duplicate comments (1)
docs/contributing.md (1)

8-10: ⚠️ Potential issue | 🟡 Minor

Use canonical shared-standard filenames to avoid link drift.

Line 8 and Line 10 point to standards/python-coding.md and standards/pull-requests.md, but repository guidance references standards/python-style-guide.md and standards/pull-request-guidelines.md. Please align these links to the canonical filenames.

Suggested fix
-- [Python coding conventions](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/python-coding.md)
+- [Python coding conventions](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/python-style-guide.md)
...
-- [Pull requests](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/pull-requests.md)
+- [Pull requests](https://github.com/softwareone-platform/mpt-extension-skills/blob/main/standards/pull-request-guidelines.md)

Based on learnings: "Follow the pull request guidelines defined in standards/pull-request-guidelines.md..." and "Applies to **/*.py : Follow the coding style and conventions defined in standards/python-style-guide.md...".

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/contributing.md` around lines 8 - 10, Update the two broken links in the
markdown list: replace references to standards/python-coding.md with
standards/python-style-guide.md and replace standards/pull-requests.md with
standards/pull-request-guidelines.md so the link targets match the canonical
filenames; also scan the same file for any other occurrences of these old names
and update them to the canonical filenames to avoid future link drift.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@docs/testing.md`:
- Around line 39-40: The docs/testing.md claim that "Branch coverage enabled" is
incorrect because pytest/cov is not configured with --cov-branch in
pyproject.toml; either add --cov-branch to the pytest-cov invocation in
pyproject.toml (so pytest respects branch coverage) or remove/update the "Branch
coverage enabled" statement in docs/testing.md to reflect current configuration;
reference the pytest/cov flag (--cov-branch) and the docs/testing.md statement
when making the change.

---

Duplicate comments:
In `@docs/contributing.md`:
- Around line 8-10: Update the two broken links in the markdown list: replace
references to standards/python-coding.md with standards/python-style-guide.md
and replace standards/pull-requests.md with standards/pull-request-guidelines.md
so the link targets match the canonical filenames; also scan the same file for
any other occurrences of these old names and update them to the canonical
filenames to avoid future link drift.
🪄 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: Repository YAML (base), Organization UI (inherited)

Review profile: CHILL

Plan: Pro

Run ID: 02abeefe-56d7-4b1f-97ca-62def285dfc3

📥 Commits

Reviewing files that changed from the base of the PR and between 4238e8e and 4a2fcbe.

📒 Files selected for processing (10)
  • .github/workflows/copilot-instructions.md
  • AGENTS.md
  • README.md
  • docs/PROJECT_DESCRIPTION.md
  • docs/contributing.md
  • docs/documentation.md
  • docs/local-development.md
  • docs/testing.md
  • docs/usage.md
  • pyproject.toml
💤 Files with no reviewable changes (1)
  • docs/PROJECT_DESCRIPTION.md
✅ Files skipped from review due to trivial changes (3)
  • pyproject.toml
  • docs/documentation.md
  • docs/usage.md
🚧 Files skipped from review as they are similar to previous changes (4)
  • .github/workflows/copilot-instructions.md
  • docs/local-development.md
  • AGENTS.md
  • README.md

Comment thread docs/testing.md
@d3rky d3rky merged commit 4e29821 into main Apr 14, 2026
4 checks passed
@d3rky d3rky deleted the feature/MPT-20094/generate-technical-documentation-for-the-repo branch April 14, 2026 15:04
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