Skip to content

fix(docs): update broken message attachments links to current developer docs URL - #9162

Open
bloodsportshooting wants to merge 1 commit into
mattermost:masterfrom
bloodsportshooting:fix/broken-message-attachments-links
Open

fix(docs): update broken message attachments links to current developer docs URL#9162
bloodsportshooting wants to merge 1 commit into
mattermost:masterfrom
bloodsportshooting:fix/broken-message-attachments-links

Conversation

@bloodsportshooting

Copy link
Copy Markdown

Summary

Two documentation pages linked to https://docs.mattermost.com/developer/message-attachments.html, which returns 404 — the message attachments reference now lives on the developer portal at https://developers.mattermost.com/integrate/reference/message-attachments/ (the URL already used elsewhere in these docs, e.g. source/end-user-guide/access/client-availability.rst and source/integrations-guide/faq.rst).

Changes

  • source/administration-guide/manage/bulk-export-tool.rst: update the message attachments link in the Post object props field description.
  • source/administration-guide/onboard/bulk-loading-data.rst: same fix for the bulk-loading Post object table.

Verification

  • Confirmed https://docs.mattermost.com/developer/message-attachments.html returns HTTP 404.
  • Confirmed the replacement URL returns HTTP 200.
  • Scanned all outbound links in the docs source; these were the only two occurrences of this broken link.

…er docs URL

The message attachments documentation moved from docs.mattermost.com/developer/
to developers.mattermost.com. Two pages (bulk-export-tool, bulk-loading-data)
still pointed at the old URL, which now returns 404. Update both to the live
URL used elsewhere in the docs.
@mattermost-build

Copy link
Copy Markdown
Contributor

Hello @bloodsportshooting,

Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Per the Mattermost Contribution Guide, we need to add you to the list of approved contributors for the Mattermost project.

Please help complete the Mattermost contribution license agreement?
Once you have signed the CLA, please comment with /check-cla and confirm that the CLA check is green.

This is a standard procedure for many open source projects.

Please let us know if you have any questions.

We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

@coderabbitai

coderabbitai Bot commented Aug 26, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 1ea3e1c7-1ec0-41ab-bf64-3018b97d16b4

📥 Commits

Reviewing files that changed from the base of the PR and between 7cf74f3 and 5d25b3a.

📒 Files selected for processing (2)
  • source/administration-guide/manage/bulk-export-tool.rst
  • source/administration-guide/onboard/bulk-loading-data.rst

Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review.


📝 Walkthrough

Walkthrough

The changes replace deprecated Mattermost documentation links with the current Developers message attachments documentation link in two administration guides.

Changes

Documentation link updates

Layer / File(s) Summary
Update Post props references
source/administration-guide/manage/bulk-export-tool.rst, source/administration-guide/onboard/bulk-loading-data.rst
The Post props field descriptions now reference the current Developers message attachments documentation.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to 5d25b

This change only replaces two broken documentation links with the current message attachments reference; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely describes the update to broken message attachments links and identifies the new developer documentation URL.
Description check ✅ Passed The description directly explains the two broken links, the replacement URL, the affected files, and the verification performed.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (2 skipped: 2 unsupported.)

✨ Finishing Touches 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@bloodsportshooting

Copy link
Copy Markdown
Author

/check-cla

2 similar comments
@bloodsportshooting

Copy link
Copy Markdown
Author

/check-cla

@bloodsportshooting

Copy link
Copy Markdown
Author

/check-cla

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants