Repository navigation
Conversation
- Automated translation status detection for p5.js examples - Detects outdated and missing translations using GitHub API - Creates GitHub issues for translation updates - Supports Spanish, Hindi, Korean, and Chinese Simplified - Action-only implementation without UI components
…in a nice expandable way
…README documentation
…generation limits per language; remove test files.
As adviced by mentor
Remove the needTranslation: true line when done
We now look at the title, body, comments, cross references to pull out the issue number(s)
…es changed/added in the PR to ensure the correct translations have been added
…equest to pull_request_target
3 tasks done
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
[This is a demonstration of how to apply the translation tracker function from v1 to v2. PLEASE DO NOT MERGE OR REVIEW]
Step 1: Cherry-pick last year's project and followups on v1:
This results in multiple merge conflicts, resolve them one by one then
git cherry-pick --continue.Notably, the JumpTo fix and the Examples attribution related updates should be manually verified. The best place to sense-check JumpTo behavior is by navigating through the tutorials, both using JumpTo and otherwise; nothing weird should happen. (Main weird thing to watch for: wrong section underlined)Step 2: Cherry-pick in this' year's project - the chronological commits of https://github.com/processing/p5.js-website/pull/1582/commits:
This should work without any merge conflicts!
Step 3 (NOT done in this branch ❗) Review all workflows and make sure they state the correct branch targets.