feat: Add move command to relocate pages by saggl · Pull Request #32 · pchuri/confluence-cli

saggl · 2026-02-11T15:04:04Z

Summary

Adds a move command to relocate Confluence pages to a new parent location.

Changes

New confluence move <pageId> <newParentId> command with optional --title flag
Implement movePage() method in ConfluenceClient
Add test coverage (2 test cases, all 42 tests passing)

Usage

Move a page:

confluence move 123456789 987654321

Move and rename:

confluence move 123456789 987654321 --title "New Title"

🤖 Generated with Claude Code

This commit adds a new `move` command that allows users to move Confluence pages to a different parent page, optionally renaming them in the process. ## Changes - Add `confluence move <pageId> <newParentId> [--title]` command to CLI - Implement `movePage()` method in ConfluenceClient class - Support moving pages by updating the ancestors array in the Confluence API ## Usage ```bash # Move a page to a new parent confluence move 123456789 987654321 # Move and rename a page confluence move 123456789 987654321 --title "New Page Title" ``` ## Implementation Details The move operation: 1. Fetches the current page to get version and content 2. Updates the page with new ancestors array pointing to new parent 3. Optionally updates the title if provided 4. Increments version number as required by Confluence API This feature enables better page organization and restructuring workflows within Confluence spaces. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Adds comprehensive test coverage for the movePage functionality to prevent regressions and document expected behavior. Tests verify basic page moves and moves with title changes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Refactor movePage method in ConfluenceClient to use destructuring and reduce verbosity while maintaining identical functionality. Remove unnecessary intermediate variables and simplify data extraction. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

This reverts commit 6a0c6c0.

Copilot

Pull request overview

Adds support for relocating Confluence pages by introducing a move command backed by a new ConfluenceClient.movePage() API, with accompanying tests.

Changes:

Added movePage(pageId, newParentId, newTitle) to update a page’s ancestors (and optionally title).
Added unit tests covering moving a page and moving+renaming.
Incremented page version during the move update request.

Reviewed changes

Copilot reviewed 2 out of 4 changed files in this pull request and generated 5 comments.

File	Description
`lib/confluence-client.js`	Implements `movePage()` by GETing the page, building an updated payload (ancestors/version/title/body), and PUTing it back.
`tests/confluence-client.test.js`	Adds tests exercising `movePage()` for move-only and move+rename scenarios.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Copilot · 2026-02-12T02:57:16Z

+  /**
+   * Move a page to a new parent location
+   */
+  async movePage(pageId, newParentId, newTitle = null) {


newTitle || title treats an empty string as falsy and will silently fall back to the original title. If callers intentionally pass an empty string (or other falsy values), this won’t be honored. Prefer nullish coalescing (newTitle ?? title) and consider defaulting newTitle to undefined to cleanly represent “not provided”.

Copilot · 2026-02-12T02:57:16Z

+    const pageData = {
+      id: pageId,
+      type: 'page',
+      title: newTitle || title,


newTitle || title treats an empty string as falsy and will silently fall back to the original title. If callers intentionally pass an empty string (or other falsy values), this won’t be honored. Prefer nullish coalescing (newTitle ?? title) and consider defaulting newTitle to undefined to cleanly represent “not provided”.

Copilot · 2026-02-12T02:57:17Z

+      const result = await client.movePage('123456789', '987654321');
+
+      expect(result.id).toBe('123456789');
+      expect(result.version.number).toBe(6);
+      expect(result.ancestors).toEqual([{ id: '987654321' }]);


These tests only assert the mocked response, not that movePage() sends the correct PUT payload (e.g., ancestors set to newParentId, version incremented, title overridden when provided, and body/space preserved). Add assertions against the captured request (e.g., via mock.history.put[0].data or an onPut matcher) to validate the behavior being introduced.

Copilot · 2026-02-12T02:57:17Z

+      mock.onGet('/content/123456789').reply(200, {
+        id: '123456789',
+        title: 'Original Title',
+        version: { number: 5 },
+        body: { storage: { value: '<p>Original content</p>' } },
+        space: { key: 'TEST' }
+      });
+
+      mock.onPut('/content/123456789').reply(200, {
+        id: '123456789',
+        title: 'Original Title',
+        version: { number: 6 },
+        ancestors: [{ id: '987654321' }]
+      });
+
+      const result = await client.movePage('123456789', '987654321');
+
+      expect(result.id).toBe('123456789');
+      expect(result.version.number).toBe(6);
+      expect(result.ancestors).toEqual([{ id: '987654321' }]);
+
+      mock.restore();
+    });
+
+    test('should move a page with new title', async () => {
+      const mock = new MockAdapter(client.client);
+
+      mock.onGet('/content/555666777').reply(200, {
+        id: '555666777',
+        title: 'Old Title',
+        version: { number: 2 },
+        body: { storage: { value: '<p>Page content</p>' } },
+        space: { key: 'DOCS' }
+      });
+
+      mock.onPut('/content/555666777').reply(200, {
+        id: '555666777',
+        title: 'New Title',
+        version: { number: 3 },
+        ancestors: [{ id: '888999000' }]
+      });
+
+      const result = await client.movePage('555666777', '888999000', 'New Title');
+
+      expect(result.title).toBe('New Title');
+      expect(result.version.number).toBe(3);
+      expect(result.ancestors).toEqual([{ id: '888999000' }]);
+
+      mock.restore();


Calling mock.restore() at the end of the test can leak the mock if the test throws/early-fails before reaching that line. Move cleanup to an afterEach(() => mock.restore()), or wrap the test body in try/finally to ensure restore always runs.

Suggested change

mock.onGet('/content/123456789').reply(200, {

id: '123456789',

title: 'Original Title',

version: { number: 5 },

body: { storage: { value: 'Original content' } },

space: { key: 'TEST' }

});

mock.onPut('/content/123456789').reply(200, {

id: '123456789',

title: 'Original Title',

version: { number: 6 },

ancestors: [{ id: '987654321' }]

});

const result = await client.movePage('123456789', '987654321');

expect(result.id).toBe('123456789');

expect(result.version.number).toBe(6);

expect(result.ancestors).toEqual([{ id: '987654321' }]);

mock.restore();

});

test('should move a page with new title', async () => {

const mock = new MockAdapter(client.client);

mock.onGet('/content/555666777').reply(200, {

id: '555666777',

title: 'Old Title',

version: { number: 2 },

body: { storage: { value: 'Page content' } },

space: { key: 'DOCS' }

});

mock.onPut('/content/555666777').reply(200, {

id: '555666777',

title: 'New Title',

version: { number: 3 },

ancestors: [{ id: '888999000' }]

});

const result = await client.movePage('555666777', '888999000', 'New Title');

expect(result.title).toBe('New Title');

expect(result.version.number).toBe(3);

expect(result.ancestors).toEqual([{ id: '888999000' }]);

mock.restore();

try {

mock.onGet('/content/123456789').reply(200, {

id: '123456789',

title: 'Original Title',

version: { number: 5 },

body: { storage: { value: 'Original content' } },

space: { key: 'TEST' }

});

mock.onPut('/content/123456789').reply(200, {

id: '123456789',

title: 'Original Title',

version: { number: 6 },

ancestors: [{ id: '987654321' }]

});

const result = await client.movePage('123456789', '987654321');

expect(result.id).toBe('123456789');

expect(result.version.number).toBe(6);

expect(result.ancestors).toEqual([{ id: '987654321' }]);

} finally {

mock.restore();

}

});

test('should move a page with new title', async () => {

const mock = new MockAdapter(client.client);

try {

mock.onGet('/content/555666777').reply(200, {

id: '555666777',

title: 'Old Title',

version: { number: 2 },

body: { storage: { value: 'Page content' } },

space: { key: 'DOCS' }

});

mock.onPut('/content/555666777').reply(200, {

id: '555666777',

title: 'New Title',

version: { number: 3 },

ancestors: [{ id: '888999000' }]

});

const result = await client.movePage('555666777', '888999000', 'New Title');

expect(result.title).toBe('New Title');

expect(result.version.number).toBe(3);

expect(result.ancestors).toEqual([{ id: '888999000' }]);

} finally {

mock.restore();

}

Copilot · 2026-02-12T02:57:17Z

+      mock.onGet('/content/123456789').reply(200, {
+        id: '123456789',
+        title: 'Original Title',
+        version: { number: 5 },
+        body: { storage: { value: '<p>Original content</p>' } },
+        space: { key: 'TEST' }
+      });
+
+      mock.onPut('/content/123456789').reply(200, {
+        id: '123456789',
+        title: 'Original Title',
+        version: { number: 6 },
+        ancestors: [{ id: '987654321' }]
+      });
+
+      const result = await client.movePage('123456789', '987654321');
+
+      expect(result.id).toBe('123456789');
+      expect(result.version.number).toBe(6);
+      expect(result.ancestors).toEqual([{ id: '987654321' }]);
+
+      mock.restore();
+    });
+
+    test('should move a page with new title', async () => {
+      const mock = new MockAdapter(client.client);
+
+      mock.onGet('/content/555666777').reply(200, {
+        id: '555666777',
+        title: 'Old Title',
+        version: { number: 2 },
+        body: { storage: { value: '<p>Page content</p>' } },
+        space: { key: 'DOCS' }
+      });
+
+      mock.onPut('/content/555666777').reply(200, {
+        id: '555666777',
+        title: 'New Title',
+        version: { number: 3 },
+        ancestors: [{ id: '888999000' }]
+      });
+
+      const result = await client.movePage('555666777', '888999000', 'New Title');
+
+      expect(result.title).toBe('New Title');
+      expect(result.version.number).toBe(3);
+      expect(result.ancestors).toEqual([{ id: '888999000' }]);
+
+      mock.restore();


Calling mock.restore() at the end of the test can leak the mock if the test throws/early-fails before reaching that line. Move cleanup to an afterEach(() => mock.restore()), or wrap the test body in try/finally to ensure restore always runs.

Suggested change

mock.onGet('/content/123456789').reply(200, {

id: '123456789',

title: 'Original Title',

version: { number: 5 },

body: { storage: { value: 'Original content' } },

space: { key: 'TEST' }

});

mock.onPut('/content/123456789').reply(200, {

id: '123456789',

title: 'Original Title',

version: { number: 6 },

ancestors: [{ id: '987654321' }]

});

const result = await client.movePage('123456789', '987654321');

expect(result.id).toBe('123456789');

expect(result.version.number).toBe(6);

expect(result.ancestors).toEqual([{ id: '987654321' }]);

mock.restore();

});

test('should move a page with new title', async () => {

const mock = new MockAdapter(client.client);

mock.onGet('/content/555666777').reply(200, {

id: '555666777',

title: 'Old Title',

version: { number: 2 },

body: { storage: { value: 'Page content' } },

space: { key: 'DOCS' }

});

mock.onPut('/content/555666777').reply(200, {

id: '555666777',

title: 'New Title',

version: { number: 3 },

ancestors: [{ id: '888999000' }]

});

const result = await client.movePage('555666777', '888999000', 'New Title');

expect(result.title).toBe('New Title');

expect(result.version.number).toBe(3);

expect(result.ancestors).toEqual([{ id: '888999000' }]);

mock.restore();

try {

mock.onGet('/content/123456789').reply(200, {

id: '123456789',

title: 'Original Title',

version: { number: 5 },

body: { storage: { value: 'Original content' } },

space: { key: 'TEST' }

});

mock.onPut('/content/123456789').reply(200, {

id: '123456789',

title: 'Original Title',

version: { number: 6 },

ancestors: [{ id: '987654321' }]

});

const result = await client.movePage('123456789', '987654321');

expect(result.id).toBe('123456789');

expect(result.version.number).toBe(6);

expect(result.ancestors).toEqual([{ id: '987654321' }]);

} finally {

mock.restore();

}

});

test('should move a page with new title', async () => {

const mock = new MockAdapter(client.client);

try {

mock.onGet('/content/555666777').reply(200, {

id: '555666777',

title: 'Old Title',

version: { number: 2 },

body: { storage: { value: 'Page content' } },

space: { key: 'DOCS' }

});

mock.onPut('/content/555666777').reply(200, {

id: '555666777',

title: 'New Title',

version: { number: 3 },

ancestors: [{ id: '888999000' }]

});

const result = await client.movePage('555666777', '888999000', 'New Title');

expect(result.title).toBe('New Title');

expect(result.version.number).toBe(3);

expect(result.ancestors).toEqual([{ id: '888999000' }]);

} finally {

mock.restore();

}

pchuri

Thanks for the PR — the new move command and ConfluenceClient.movePage() implementation look solid, and local npm test / npm run lint are green.

A few suggestions:

Scope/behavior for cross-space moves
movePage() always sends space: { key: space.key } from the current page in the update payload. If cross-space moves are not intended/supported, it might be worth explicitly guarding/documenting “same-space only” (or surfacing a clearer error when the new parent is in a different space). If cross-space moves are intended, the payload/validation likely needs more thought.
Docs
README’s Commands table and examples don’t mention move yet. Adding an entry + a short usage example (including --title) would help discoverability.
CLI argument consistency
Many commands accept <pageId_or_url>, but move currently requires numeric IDs for both pageId and newParentId. Consider either:

supporting URLs by reusing the existing ID extraction helper, or
documenting clearly that move expects IDs.

Addresses PR pchuri#32 review feedback: - Add URL support for both pageId and newParentId parameters for consistency with other commands - Add validation to prevent cross-space moves with clear error messages - Add comprehensive documentation to README including usage examples and command table entry - Add test coverage for URL support and cross-space validation Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

# [1.16.0](v1.15.1...v1.16.0) (2026-02-13) ### Features * Add move command to relocate pages ([#32](#32)) ([a37f9b8](a37f9b8))

github-actions · 2026-02-13T02:39:24Z

🎉 This PR is included in version 1.16.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

saggl and others added 5 commits February 11, 2026 12:33

Remove CI workflows

6a0c6c0

test: add coverage for movePage method

073b13b

Adds comprehensive test coverage for the movePage functionality to prevent regressions and document expected behavior. Tests verify basic page moves and moves with title changes. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

Revert "Remove CI workflows"

d7be382

This reverts commit 6a0c6c0.

pchuri requested a review from Copilot February 12, 2026 02:56

Copilot AI reviewed Feb 12, 2026

View reviewed changes

pchuri reviewed Feb 12, 2026

View reviewed changes

saggl requested a review from pchuri February 12, 2026 15:00

pchuri merged commit a37f9b8 into pchuri:main Feb 13, 2026
5 checks passed

github-actions Bot pushed a commit that referenced this pull request Feb 13, 2026

chore(release): 1.16.0 [skip ci]

42aa3e9

# [1.16.0](v1.15.1...v1.16.0) (2026-02-13) ### Features * Add move command to relocate pages ([#32](#32)) ([a37f9b8](a37f9b8))

github-actions Bot added the released label Feb 13, 2026

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

feat: Add move command to relocate pages#32

feat: Add move command to relocate pages#32
pchuri merged 6 commits intopchuri:mainfrom
saggl:feature/add-move-command

saggl commented Feb 11, 2026 •

edited

Loading

Uh oh!

Copilot AI left a comment

Uh oh!

Copilot AI Feb 12, 2026

Uh oh!

Copilot AI Feb 12, 2026

Uh oh!

Copilot AI Feb 12, 2026

Uh oh!

Copilot AI Feb 12, 2026

Uh oh!

Copilot AI Feb 12, 2026

Uh oh!

pchuri left a comment

Uh oh!

Uh oh!

github-actions Bot commented Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

Conversation

saggl commented Feb 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Summary

Changes

Usage

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Copilot AI Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

pchuri left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

github-actions Bot commented Feb 13, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

saggl commented Feb 11, 2026 •

edited

Loading