Show HN: Yuki-no – GitHub Action that makes docs translation projects trackable

Hey HN, I created Yuki-no while maintaining the official Vite Korean documentation translation project.

Translation work requires meticulous tracking of changes in the original documentation. Without this, translators might translate incorrect content or miss important sections.

Previously, we used Ryu-Cho(https://github.com/vuejs-translations/ryu-cho) for tracking. This open source tool uses GitHub Actions to register changes in the original repository as GitHub Issues in the translation repository. However, after using it for nearly two years, I identified several issues:

1. When GitHub Actions failed, all in-progress commits were lost, causing us to miss portions of the original content 2. The approach for filtering target files was very limited (based on `startsWith` string prefix comparison) 3. Inability to set labels on GitHub Issues made them difficult to distinguish from other issues at a glance 4. No way to identify whether translation-related commits were released, potentially causing premature translation of unreleased content

Yuki-no solves these problems with:

- Improved Action stability through batch processing (verified to work correctly for over 200 commits) - Automatic recovery from failures in subsequent runs - Release tracking feature - Glob pattern-based target files filtering - Custom label settings for created issues

It's currently used in:

- Official Vite Korean documentation project - Vue.js Korean documentation project - Vite documentation translation template

Example issues: https://github.com/vitejs/docs-ko/issues?q=is%3Aissue+label%...

If you're planning to start a translation project, need help with migration or configuration, or are interested in the project, feel free to reach out through GitHub issues or email me at to@shj.rip!