Command Reference
Format
/gpt-translate [input filepath] [output filepath] [target language]Comment
Create a comment with /gpt-translate or /gt in an issue or pull request.
You can use /gt as a shorthand for /gpt-translate.
PR will be created
Translated files will be created as a pull request. 
In other words, if you keep commenting on an issue, new PRs will continuously be created. If you keep commenting on a PR, new commits will continuously be added to that PR.
Examples
Single File
/gpt-translate ./README.md ./JA/README.md JapaneseThe following directory structure changes are expected when this command is executed.
Before
After
- README.md
README.md in the root is newly translated into Japanese as README.md under the JA directory.
Multiple Files
The input file specification method has been expanded since v1.1.6. Please refer to the Path Specification page for details.
/gpt-translate ./EN/*.md ./JA/*.md JapaneseThe following directory structure changes are expected when this command is executed.
Before
- getting-started.md
- setup.md
- hoge.webp
After
- getting-started.md
- setup.md
- hoge.webp
- getting-started.md
- setup.md
All markdown files under the EN directory will be translated and output under the new JA directory.
Tips
GitHub comments support markdown notation, so if you use an asterisk(*), it will be converted to italic type.
This will still recognize the command normally, but it is recommended to enclose the command in codespan (`).