Skip to content

Conversation

@its-miroma
Copy link
Member

I'm waiting for Modrinth to confirm that their workflows are licensed under MIT.

Please read through the commit messages, which contain important context and summary

@its-miroma its-miroma added framework Related to the VitePress framework i18n-l10n Related to internationalization or to localization through Crowdin labels Dec 27, 2025
@netlify
Copy link

netlify bot commented Dec 27, 2025

Deploy Preview for nimble-elf-d9d491 ready!

Name Link
🔨 Latest commit 44fb11a
🔍 Latest deploy log https://app.netlify.com/projects/nimble-elf-d9d491/deploys/6956f921e881280008a993e9
😎 Deploy Preview https://deploy-preview-439--nimble-elf-d9d491.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@its-miroma its-miroma force-pushed the action branch 2 times, most recently from 890435c to 640a654 Compare December 27, 2025 15:17
Copy link
Member

@modmuss50 modmuss50 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some minor points, we should ideally wait for MR to confirm the license.

`publish.yml` only ran additional steps on top of `build.yml`'s, so we
can stay DRY by moving the `deploy` job to `build.yml`.

This has the (positive?) side effect of requiring success in building
the mod and running its game tests before changes are deployed to prod.

Other changes:

- rename `build.yml` to `build.yaml`, see <https://yaml.org/faq>
- use "temurin" as Java distribution, which we recommend in the docs
- publish checkstyle report before checking datagen
- extend the `format` workflow to also check that files are Prettier
- rename `markdownlint.yml` to `format.yaml`
- avoid fetching all repo history, not needed
inspired by <https://github.com/modrinth/code/tree/7de4e55badd38aa969fb7181f5889e9f03ab757b/.github/workflows>

Co-authored-by: Cal H. <contact@cal.engineer>
Co-authored-by: Prospector <6166773+Prospector@users.noreply.github.com>

Other changes:

- lock third-party actions to a commit hash
- use peculiar naming for commits, inspired by old Minecraft snapshots
- add caching when pushing sources, which allows Crowdin to push diffs
- add `preserve_hierarchy` and `project_id` to `crowdin.yaml`.
  see <https://github.com/crowdin/github-action#migration-from-the-native-github-integration>

Important note regarding the implementation:

the action currently creates a branch i18n/main on the main repo and
opens a PR to main. This requires changing an option in the repo's
settings to allow Actions to create PRs to the same repo.

alternatively, the action authors recommend setting it up with a machine
account, such as FabricMCBot, who would fork the repo, push translations
to their own branch, and open a PR to upstream.

see <https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#push-pull-request-branches-to-a-fork>
"Internationalization [i18n] is the design and development of a product
[...] that enables easy localization [...]."

"Localization [l10n] refers to the adaptation of a product [...] to meet
the language [...] of a specific target marker (a 'locale')."

see <https://www.w3.org/International/questions/qa-i18n>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

framework Related to the VitePress framework i18n-l10n Related to internationalization or to localization through Crowdin

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants