fix(ci): use Github Bot for Crowdin

[avivkeller]

Ref: #7668
Ref: https://github.com/stefanzweifel/git-auto-commit-action#commits-made-by-this-action-do-not-trigger-new-workflow-runs

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
nodejs-org	✅ Ready (Inspect)	Visit Preview	Apr 22, 2025 2:56pm

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.61%. Comparing base (c6b6928) to head (644c28a).

✅ All tests successful. No failed tests found.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #7671   +/-   ##
=======================================
  Coverage   74.61%   74.61%           
=======================================
  Files          96       96           
  Lines        7689     7689           
  Branches      192      192           
=======================================
  Hits         5737     5737           
  Misses       1950     1950           
  Partials        2        2           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[avivkeller]

@ovflowd can you please update this PR with the crowdin bot secret, I'm not sure what the secret is labeled

[ovflowd]

@ovflowd can you please update this PR with the crowdin bot secret, I'm not sure what the secret is labeled

What sort of permissions you need for the Access Token?

[avivkeller]

contents and pull_request write

[ovflowd]

contents and pull_request write

I mean, GitHub Developer Access Token permissions; What scopes?

[avivkeller]

I mean, GitHub Developer Access Token permissions; What scopes?

Assuming the token is fine-grained,
"Pull requests" repository permissions (write)
"Contents" repository permissions (write)

Assuming the token is classic,
repo (public_repo should also work)

[ovflowd]

Token created. It expires in 2026 (April 30) -- Name: CROWDIN_GITHUB_BOT_TOKEN

cc @mcollina apparently the Node.js Enterprise sets a limit of how long tokens can last. Can we change that from a maximum of 366 days to no expiration?

[avivkeller]

It worked!

https://github.com/nodejs/nodejs.org/actions/runs/14597939715/

[github-actions]

Lighthouse Results

URL	Performance	Accessibility	Best Practices	SEO	Report
/en	🟢 99	🟢 100	🟢 100	🟢 91	🔗
/en/about	🟢 100	🟢 100	🟢 100	🟢 91	🔗
/en/about/previous-releases	🟢 99	🟢 100	🟢 100	🟢 92	🔗
/en/download	🟢 98	🟢 100	🟢 100	🟢 91	🔗
/en/blog	🟢 100	🟢 100	🟢 96	🟢 92	🔗

[avivkeller]

FYI I've closed the currently open Crowdin PRs, and will make a new one once this lands.

[avivkeller]

Fast tracking, as this doesn't change the execution of anything, only the permissions granted.

[ovflowd]

Fast tracking, as this doesn't change the execution of anything, only the permissions granted.

The author of the PR cannot request for fast-tracking and approve the fast-tracking. So if you say requesting fast tracking, someone needs to give a 👍 first 🙈

[avivkeller]

😅