Skip to content

Conversation

@tasshi-me
Copy link
Member

@tasshi-me tasshi-me commented Nov 12, 2025

Why

Adding a Troubleshooting section improves usability and helps users quickly resolve common errors without needing to search external resources.

What

  • Add a Troubleshooting section to the README (ja, en)
    • Covers common issues such as:
      • Connection errors (base URL, proxy, retry)
      • Authentication errors (credentials, secure access domain)
      • Permission errors (access rights, guest space, API token scopes)

How to test

  • Check that the new “Troubleshooting” section renders correctly in both README.md and README_en.md
  • Confirm internal links and formatting (e.g., headings, code blocks) display properly on GitHub

Checklist

  • Updated documentation if it is required.
  • Added tests if it is required.
  • Passed pnpm lint and pnpm test on the root directory.

@tasshi-me tasshi-me marked this pull request as ready for review November 12, 2025 16:45
@tasshi-me tasshi-me requested a review from a team as a code owner November 12, 2025 16:45
@tasshi-me tasshi-me requested review from chihiro-adachi and shabaraba and removed request for a team November 12, 2025 16:45
@tasshi-me tasshi-me merged commit 2a89bfe into main Nov 19, 2025
11 checks passed
@tasshi-me tasshi-me deleted the fix/add-trouble-shooting branch November 19, 2025 06:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants