pipewell-confluence-publisher 1.0.1

Publish Markdown documentation from GitHub to Confluence Cloud or Data Center

confluence-publisher

A one-way publishing pipeline that syncs GitHub Markdown files to Confluence pages.

GitHub is the source of truth. Confluence is the generated presentation layer.

---

Quick start

1. Add a confluence-manifest.yaml to your repository root.
2. Copy an example workflow from examples/workflows/ into .github/workflows/.
3. Add the three required secrets/variables to your repository settings.
4. Push or trigger manually — pages appear in Confluence within minutes.

See docs/ONBOARDING.md for a full step-by-step guide.

# confluence-manifest.yaml
defaults:
  space_id: ENG
  parent_id: '123456'

pages:
  docs/architecture.md:
    title: Architecture Overview
    page_id: '234567'         # existing Confluence page ID
  docs/runbook.md:
    title: Operations Runbook # no page_id — auto-created on first publish

# .github/workflows/publish-to-confluence.yml (minimal)
- uses: pipewell/confluence-publisher@v1
  with:
    confluence-base-url: ${{ vars.CONFLUENCE_BASE_URL }}
    confluence-api-token: ${{ secrets.CONFLUENCE_API_TOKEN }}
    confluence-email: ${{ vars.CONFLUENCE_EMAIL }}

---

What it does

• Triggers on push to main when files under docs/**/*.md change
• Converts Markdown to Confluence Storage Format using a custom mistletoe renderer
• Manages page identity via a checked-in YAML manifest (page IDs, not titles)
• Auto-creates pages when page_id is absent; writes the new ID back via a [skip ci] commit
• Uploads local images and Mermaid diagrams as page attachments
• Detects edit conflicts (Confluence version ahead of last published) and warns or fails
• Stores the Git commit SHA in the Confluence version message for traceability
• Treats missing images, Mermaid render failures, and upload errors as hard build failures

---

Failure semantics

All failures exit non-zero. There are no silent failures.

Failure	Behaviour
Markdown conversion error	Build fails; page not published
Local image not found on disk	Build fails; page not published (pre-flight check)
mmdc not installed with Mermaid diagrams present	Build fails; page not published
Mermaid render failure	Build fails; page not published
Confluence API error on create or update	Build fails; manifest unchanged
Attachment upload failure on a new page	Build fails; placeholder body stays in Confluence; page_id written to manifest; next push retries via the update path (no duplicate page created)
Attachment upload failure on an existing page	Build fails; page body not updated; manifest hash unchanged; next push retries
Manual edit conflict	Warning logged; page overwritten with GitHub content. --strict-conflicts makes this a build error while still overwriting

The "Commit manifest state" step uses if: always() so page_id values are committed to the repo even when the publish step exits non-zero, preserving the retry guarantee across CI runs.

---

Supported Markdown

Feature	Support
Headings H1-H6	Full
Bold, italic, inline code	Full
Fenced code blocks with language label	Full
Tables	Full
Ordered and unordered lists (including nested)	Full
Blockquotes	Full
Horizontal rules	Full
External links	Full
Internal links between managed .md files	Resolved to Confluence page links
Local images	Uploaded as page attachments
External images	Rendered inline
Mermaid diagrams	Rendered to PNG via mmdc (requires Node in CI)
Strikethrough	Not supported -- raises a conversion error
Raw HTML	Not supported -- raises a conversion error

---

Scope

This tool is intentionally narrow:

• One-way only. It does not sync Confluence edits back to GitHub.
• Not a real-time mirror. It runs on push and on a nightly validation schedule.
• Not a general-purpose renderer. It targets the Confluence Storage Format features needed for engineering documentation.

---

Documents

Document	Purpose
ONBOARDING	Step-by-step guide for connecting a new repository
MANIFEST_SPEC	Full manifest format reference
ARCHITECTURE	System design and component breakdown
DECISIONS	Decision log with rationale
BRD	Business requirements and success metrics
TRD	Technical requirements and API reference
DELIVERY_PLAN	Phased delivery history