When changes are saved in TinaCMS, they are committed to your project's GitHub repository. By default, these commits are authored by our tina-cloud-app
, which can make it difficult to track who made specific changes within a team.
To solve this, TinaCMS provides two distinct methods for attributing your work: Act as You (the recommended approach) or Co-authoring.
You can choose between two levels of GitHub integration:
tina-cloud-app
will still make the commit, but it will add your name and email as a co-author, attributing the change to you in the commit message.This method provides perfect attribution by using your GitHub account to perform all actions. Commits, branches, and pull requests will appear in your repository's history exactly as if you had made them from your own computer.
An action is only allowed if both your personal user account and the bot have the required permissions.
Code
(Read & Write)Pull Requests
(Read & Write)Repository Hooks
(Read & Write)Metadata
(Read-only)You can find more information in the Authenticating with a GitHub App on behalf of a user docs
If you initiate an action that your personal GitHub account does not have permission for, the action will automatically fall back to being performed by the bot's identity.
If you prefer not to grant the application permission to act on your behalf, co-authoring provides a lighter-weight way to get attribution.
With this option, the tina-cloud-app
still performs all Git actions, but it adds a Co-authored-by:
trailer to the end of each commit message, crediting you for the work.
Note on Email Privacy: The co-author email is publicly viewable on GitHub. If you wish to keep your email private, GitHub provides anoreply
email address you can use. You can find this in your GitHub email settings.
Feature | Act as You (Recommended) | Co-authoring |
---|---|---|
Attribution Method | Commits are made directly by your user identity. | Commits are made by the bot, with your name added as a |
Security & Permissions | Actions are limited by both the app's and your own permissions. | No extra permissions required. Relies only on the bot's permissions. |
Setup | One-time GitHub OAuth authorization. | Manual entry of your name and email. |
Best For | Teams wanting seamless, accurate attribution and a clear commit history. | Users who want attribution without authorizing the app to act on their behalf. |