tauri-apps / tauri-apps/tauri-docs
Fix i18n builder script for Netlify PRs
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 1.1k
- Forks
- 887
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 48
Description
There seems to be an issue that's causing the i18n-tracker to fail and break any Netlify deploy previews (even though the build is successful).
Example logs:
https://app.netlify.com/sites/tauri-docs-starlight/deploys/64d15e5677826f0008f238cf#L350
https://app.netlify.com/sites/tauri-docs-starlight/deploys/64da1aa2fb11240008024a18
I haven't debugged it fully yet, but I'm wondering if it's a GitHub rate limit or something with git history (used to generate the status). Anytime I go onto a deploy preview and force-build it (reset cache, etc.) then it seems to build fine.
Example PR where this is happening: https://github.com/tauri-apps/tauri-docs/pull/1367. Note it says deploy failed but that's because Netlify doesn't update the deploy status on GitHub after you manually re-trigger it in the Netlify UI.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with packages/i18n-tracker and inspect the example Netlify logs and PR 1367 deploy preview. Determine why the tracker fails during Netlify previews, then verify that the tracker completes successfully on a preview build without requiring a manual cache-reset rebuild.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100