Automatically commit translation files to GitHub

This feature is currently in Beta. We welcome your feedback.

Adding GitHub as a deployment host

• Open the developer tools modal from any project view where you see the :wrench icon:
• Switch to the "Deployments" tab, and click the "New host" link
• Choose "GitHub", enter your credentials, and confirm with "Add repo".

Nothing is committed yet. You've just created a destination for publishing files. See general instructions on publishing files to a host.

GitHub settings:

• API Key
  Keys can be generated from your GitHub profile developer settings. We recommend a "Fine-grained Personal Access Token" with read/write access to the contents of ONLY the repository defined for this host.

• Repository
  Enter your unique repository URI in the form OWNER/REPO. Don't include any sub path information here. Directory paths inside the repo can be defined by each deployment you commit.

• Branch
  The Git branch defaults to "main" but older repositories commonly use "master". We recommend you test your Loco deployments in a non-production branch until you're happy the process is reliable. Note that the branch must exist; Loco won't create it.

• Message
  This is the text used for all commit messages via this host configuration. It's static text, and doesn't vary according to the nature of the changes being committed.

Limitations

• Loco won't commit to an empty repository. Add at least one file first.
• Personal Access Tokens are currently the only authentication method.
• Git deployment is one-way. Loco never deletes, or moves any files it has committed.