Subtree pull Scribe-i18n

[wkyoshida]

Contributor checklist

• This pull request is on a separate branch and not the main branch

---

Description

Just an example of how the workflow might look like..

• Running the following in project root to pull in changes from Scribe-i18n:
  git subtree pull --prefix Scribe/i18n [email protected]:scribe-org/Scribe-i18n.git main --squash
• Then two commits as seen here in this PR get auto-created

I'll look into formalizing the documentation for this over the weekend. It'll likely be best to have a generic version in the Scribe-i18n repo, but then quick repo-specific ones for each project.

P.S. Cool to see, though, that the command still appears to work despite other updates having occurred without using the command. The diff here likely appears empty, since I'd guess the manual updates to the i18n folder still matched, which is a good sign.

Related issue

• 🌐

[github-actions]

Thank you for the pull request!

The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :)

If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and iOS rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you!

Maintainer checklist

• The commit messages for the remote branch should be checked to make sure the contributor's email is set up correctly so that they receive credit for their contribution

  • The contributor's name and icon in remote commits should be the same as what appears in the PR
  • If there's a mismatch, the contributor needs to make sure that the email they use for GitHub matches what they have for git config user.email in their local Scribe-iOS repo

• The linting and formatting workflows within the PR checks do not indicate new errors in the files changed

• The CHANGELOG has been updated with a description of the changes for the upcoming release and the corresponding issue (if necessary)

[wkyoshida]

btw - attempting to run the same command again logs out the following message

From github.com:scribe-org/Scribe-i18n
 * branch            main       -> FETCH_HEAD
Subtree is already at commit 812482a104212e84ccb7aa620e580e9130a6581b.

nice

[andrewtavis]

This is one cool looking commit to branch visual :)

[andrewtavis]

CC @Jag-Marcel, as this PR has some info we were discussing :)

[andrewtavis]

Nice and I was able to bring in the most recent changes in 900d068 😊