Add troubleshooting entry for load-test-ng and Mattermost version compatibility

[fmartingr]

Summary

• Add a new troubleshooting entry to docs/faq.md documenting the 501 error when running load-test-ng v1.30.0+ against Mattermost servers older than v11.0.1
• The GetClientConfig API changed in Mattermost v11.0.1; load-test-ng v1.30.0+ uses the new endpoint, causing failures on older servers
• Recommends using load-test-ng v1.29.0 or earlier for pre-v11 deployments

Test plan

• Verify the new FAQ entry renders correctly in markdown
• Confirm the changelog link resolves to the correct releases page

Summary by CodeRabbit

• Documentation
  • Minor README formatting cleanup for consistency.
  • Improved FAQ formatting for clarity and added a new entry explaining 501 errors when using load-test-ng v1.30.0+ against older servers, with recommended downgrade to v1.29.0 (or earlier) and links to relevant changelog/troubleshooting guidance.

[Copilot]

Pull request overview

Adds documentation to help users troubleshoot load-test-ng compatibility issues when running against older Mattermost server versions, and cleans up minor markdown formatting/whitespace.

Changes:

• Re-indents markdown list/code blocks in docs/faq.md for cleaner rendering.
• Adds a new FAQ troubleshooting entry describing a 501 error when load-test-ng v1.30.0+ targets Mattermost < v11.0.1, with a recommended workaround.
• Removes trailing whitespace at the end of README.md.

Reviewed changes

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

File	Description
docs/faq.md	Markdown formatting tweaks + new troubleshooting entry for 501 errors due to Mattermost version/API compatibility.
README.md	Removes a trailing blank/whitespace line at EOF.

---

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

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 62e027ad-eafc-49b3-944e-cd5602bccbb7

📥 Commits

Reviewing files that changed from the base of the PR and between 73b484a and 579aac5.

📒 Files selected for processing (1)

• docs/faq.md

🚧 Files skipped from review as they are similar to previous changes (1)

• docs/faq.md

---

📝 Walkthrough

Walkthrough

Documentation-only changes: removed a trailing empty newline in README.md, adjusted code block indentation/spacing in docs/faq.md, and added a new FAQ subsection describing a compatibility issue between load-test-ng v1.30.0+ and Mattermost servers older than v11.0.1 with a recommended workaround.

Changes

Cohort / File(s)	Summary
Documentation README.md, docs/faq.md	Removed an empty trailing newline in README.md; reformatted code block indentation/spacing in docs/faq.md; added a FAQ subsection describing a 501 error when using load-test-ng v1.30.0+ against Mattermost < v11.0.1 and recommending v1.29.0 or earlier.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the main change: adding a troubleshooting entry for load-test-ng and Mattermost version compatibility to the FAQ documentation.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch readme/versioning

📝 Coding Plan

• Generate coding plan for human review comments

---

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

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[agarciamontoro]

Thank you for this, @fmartingr!