[PR] feat(bitbucket): add read-only PR commits fetch [magpie]

["KatalKavya96 (via GitHub)" <gi...@apache.org>]

KatalKavya96 opened a new pull request, #797:
URL: https://github.com/apache/magpie/pull/797

   <!-- SPDX-License-Identifier: Apache-2.0
        https://www.apache.org/licenses/LICENSE-2.0 -->
   
   ## Summary
   
   * Adds `magpie-bitbucket pr commits <id>` as a read-only Bitbucket change-request operation.
   * Fetches commits associated with a pull request from both Bitbucket Cloud and Bitbucket Data Center with pagination.
   * Normalizes commit output into `commits[]` with hash, message, author, date, links, and raw payloads, without adding any write or repository mutation path.
   
   ## Type of change
   
   * [ ] Skill change (`.claude/skills/<name>/`) — eval fixtures updated below
   * [x] Tool / bridge contract (`tools/<system>/*.md`)
   * [x] Python package (`tools/*/` with `pyproject.toml`)
   * [ ] Groovy reference impl
   * [x] Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
   * [x] Documentation (`docs/`, `README.md`, `CONTRIBUTING.md`)
   * [ ] Project template (`projects/_template/`)
   * [x] CI / dev loop (`prek`, workflows, validators)
   * [ ] Other:
   
   ## Test plan
   
   * [x] `prek run --all-files` passes
   * [x] For Python packages touched: `uv run pytest` / `ruff check` / `mypy` passes
   * [ ] For Groovy bridges touched: command-line invocation tested end-to-end
   * [ ] For skill changes: eval suite passes for the affected skill
     (`PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner tools/skill-evals/evals/<skill>/`)
   * [ ] For skill *behaviour* changes: a new or updated eval fixture is included in this PR
     (a regression test for the bug fixed / the behaviour added — see CONTRIBUTING.md)
   * [x] Other: verified targeted Bitbucket tests with `PYTHONPATH=src uv run --group dev pytest tests/test_bitbucket.py`
   
   ## RFC-AI-0004 compliance
   
   * [x] **HITL** — no new mutation is added; the command is read-only
   * [x] **Sandbox** — no new unrestricted host access; Bitbucket network reach remains declared in the adapter
   * [x] **Vendor neutrality** — extends the existing Bitbucket `contract:change-request` / `Coverage: partial-read-only` adapter without introducing a new Bitbucket-specific capability contract
   * [x] **Conversational + correctable** — no new autonomous decision path is added
   * [x] **Write-access discipline** — this PR only reads pull-request commits and does not mutate branches, refs, repository history, PR state, comments, approvals, or builds
   * [x] **Privacy LLM** — fetched commit messages and raw payloads remain external data and are emitted as read-only bridge output for the caller to handle under the existing privacy/approved-LLM rules
   
   ## Linked issues
   
   Refs #606
   
   ## Notes for reviewers (optional)
   
   This is the next read-only Bitbucket follow-up after the PR discussion and PR status work.
   
   The new command is:
   
   ```bash
   magpie-bitbucket pr commits <id>
   ```
   
   It fetches commits associated with a pull request:
   
   * Bitbucket Cloud: PR commits endpoint with Cloud pagination.
   * Bitbucket Data Center: PR commits subresource with `start` / `nextPageStart` pagination.
   
   This intentionally keeps the scope to read-only commit metadata. It does not mutate branches, refs, repository history, PR state, comments, approvals, merge state, or Pipelines/builds.
   
   Docs were updated in the Bitbucket README, spec-loop adapter inventory, and labels/capabilities inventory to reflect the new partial read-only commit coverage.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] feat(bitbucket): add read-only PR commits fetch [magpie]

["KatalKavya96 (via GitHub)" <gi...@apache.org>]

KatalKavya96 commented on PR #797:
URL: https://github.com/apache/magpie/pull/797#issuecomment-4932501539

   Hi @potiuk , I opened the next Bitbucket follow-up PR for #606.
   
   This adds `magpie-bitbucket pr commits <id>` as a read-only commit fetch operation under the existing `contract:change-request` + `Coverage: partial-read-only` model.
   
   The implementation fetches commits associated with a pull request from both Bitbucket Cloud and Bitbucket Data Center with pagination, then normalizes them into `commits[]` with commit hash, message, author, date, links, and raw payloads.
   
   I also updated the Bitbucket README, spec-loop adapter docs, and labels/capabilities inventory so the documented coverage matches the new behavior. After self-review, I adjusted the README wording to present this as a `commits[]` supplement rather than implying a new formal `get_commits` contract verb.
   
   `prek run --all-files` is passing.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

Re: [PR] feat(bitbucket): add read-only PR commits fetch [magpie]

["potiuk (via GitHub)" <gi...@apache.org>]

potiuk merged PR #797:
URL: https://github.com/apache/magpie/pull/797


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@magpie.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org