-
Notifications
You must be signed in to change notification settings - Fork 630
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[JA] Proofreading on GitHub Actions #185
[JA] Proofreading on GitHub Actions #185
Conversation
Nice! I'll have a look through this week and will test some things. |
.github/workflows/ja.yaml
Outdated
- name: Set up Python | ||
uses: actions/setup-python@v1 | ||
with: | ||
python-version: "3.7" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make the python version 3.6.
Google is at this version so we can;t test anything beyond 3.6.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK. I fixed it!
Hi @sfujiwara , do you know if redpen has a list of supported languages somewhere? I recall it not working for Korean, are there any other restrictions? You are using this to maintain a translation glossary, yes? (I'm just wondering if other communities can use this setup, as well) |
@lamberta RedPen has various kinds of validators for example sentence length, invalid words, and so on. Some validators does not support Korean. But, other validators supports all languages including Korean. I guess RedPen and GitHub Actions are useful for other communities! |
Hi, how is it going on this PR? |
For example: | ||
|
||
```shell script | ||
./tools/ja/bin/proofreading.sh site/ja/guide |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this locally and seems to work ... I used homebrew to install the redpen package, probably out of scope to provide detailed install instructions, but maybe mention the Java dependency---speaking of Java, will this run in the GitHub Actions VM?
There was a log of noise at the command-line when running this, is that usual? Any way to filter out all these deprecation warnings?
Thanks for the bump on this @sfujiwara (been swamped in email lately). Tested locally and over here: lamberta#6 As long as this is restricted to the ja/ translations then seems fine. Long-term, I'll need your help to maintain this and update if there are structural changes to the docs (things move around). If that's ok with you, then we can merge. |
@lamberta OK. We will maintain and improve the proofreading tool to make our translation tasks efficient! |
Co-authored-by: Billy Lamberta <[email protected]>
Hi @lamberta
I added a minor change for the above proposal.
Currently it works on my repository and GitHub Actions (I will delete this repository if this PR is merged): |
Thanks @sfujiwara for the updates. @MarkDaoust and @yashk2810 if there's no objections, I'll merge this for the ja folks. If there are maintenance concerns or changes needed, we can loop in @sfujiwara |
LGTM. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds good. We'll keep an eye on it and will loop you in if there ae any issues. Thanks!
@lamberta
Japanese reviewers: @ohtaman, @masa-ita, @AseiSugiyama, @yukinagae, @nuka137, @chie8842, @kiszk
This PR is a proposal of #144
This PR allows us to automatically apply proofreading tool on GitHub Actions.
It would be a great help for Japanese document reviewers and translators.
I'm happy to hear your opinion about this PR!
Files and directories
.github/workflows/ja.yaml
This workflow runs only when directories and files below are changed:
tools/ja/
This is a proofreading tool used in Japanese community.
Resulting outputs
We can see the result of proofreading on GitHub PR.
The CI would fail if there are too many errors:
We can find the detailed results in GitHub Actions log: