You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@magpie.apache.org by "KatalKavya96 (via GitHub)" <gi...@apache.org> on 2026/07/04 16:53:54 UTC

Re: [I] feat(tools/bitbucket): Bitbucket forge + tracker bridge (Atlassian) [magpie]

KatalKavya96 commented on issue #606:
URL: https://github.com/apache/magpie/issues/606#issuecomment-4883129111

   @potiuk  I have started studying the existing tool patterns for this issue.
   
   From the current `main`, I noticed that `tools/github/` provides the main forge/tracker capability reference, `tools/jira/` gives the closest Atlassian REST bridge implementation pattern, and `tools/gitlab/` is still not present yet since #305 is open.
   
   Would it make sense to approach `tools/bitbucket/` in phased PRs?
   
   My proposed split is:
   
   1. **PR 1 — Initial Bitbucket bridge skeleton + read-only foundation**
   
      * Add `tools/bitbucket/`
      * Document capability, config, Cloud vs Data Center model, output contract, and write-path discipline
      * Add initial read-only commands such as auth/preflight, repo metadata, and open PR listing/fetching
      * Add mocked tests for Cloud/Data Center response normalisation
   
   2. **PR 2 — Change-request / PR operations**
   
      * Map Bitbucket pull requests to the `contract:change-request` verbs: list/get/discussion/status
      * Add review/comment/approve/decline/merge paths after the read-only base is stable
   
   3. **PR 3 — Tracker support**
   
      * Add Bitbucket Issues support where available
      * Clarify Jira handoff for adopters using Jira as the tracker and Bitbucket as the forge
   
   4. **PR 4 — Branch permissions + Pipelines**
   
      * Add branch restriction/permission reads
      * Add Bitbucket Pipelines status reads for PR/status checks
   
   I am planning to keep the first PR small and reviewable, likely focused on the bridge contract plus read-only operations, before adding write operations. Please let me know if you prefer a different first slice. Thanks!
   


-- 
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