Skip to content

Commit

Permalink
Capitalize the H in GitHub
Browse files Browse the repository at this point in the history
  • Loading branch information
cassidoo committed Oct 30, 2023
1 parent 8b8a6c9 commit 56cbd96
Show file tree
Hide file tree
Showing 14 changed files with 23 additions and 23 deletions.
2 changes: 1 addition & 1 deletion .github/SUPPORT.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,6 @@ coming down the line. If you are exited about TinaCMS, help us grow the communit
- [Docs](https://tinacms.org/docs/)
- [Slack](https://tinacms.slack.com)
- [Forum](https://community.tinacms.org/)
- [Github](https://github.com/tinacms/tinacms)
- [GitHub](https://github.com/tinacms/tinacms)
- [Submit a Bug Report](https://github.com/tinacms/tinacms/issues/new?labels=bug&template=bug-report.md)
- [Submit a Feature Request](https://github.com/tinacms/tinacms/issues/new?labels=enhancement&template=feature-request.md)
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,7 +34,7 @@ Visit [Tina's documentation](https://tina.io/docs/) to learn more.
[![Tweet](https://img.shields.io/twitter/url/http/shields.io.svg?style=social)](https://twitter.com/intent/tweet?url=https%3A%2F%2Ftinacms.org&text=I%20just%20checked%20out%20@tinacms%20on%20GitHub%20and%20it%20is%20sweet%21&hashtags=TinaCMS%2Cjamstack%2Cheadlesscms)
[![Forum](https://shields.io/github/discussions/tinacms/tinacms)](https://github.com/tinacms/tinacms/discussions)

Visit the [Github Discussions](https://github.com/tinacms/tinacms/discussions) or our [Community Discord](https://discord.com/invite/zumN63Ybpf) to ask questions, or look us up on on Twitter at [@tinacms](https://twitter.com/tinacms).
Visit the [GitHub Discussions](https://github.com/tinacms/tinacms/discussions) or our [Community Discord](https://discord.com/invite/zumN63Ybpf) to ask questions, or look us up on on Twitter at [@tinacms](https://twitter.com/tinacms).

<!-- ## Changelog
Expand Down
2 changes: 1 addition & 1 deletion examples/basic-iframe/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,6 @@ To learn more about Tina, take a look at the following resources:
- [Getting starter guide](https://tina.io/guides/tina-cloud/starter/overview/)


You can check out [Tina Github repository](https://github.com/tinacms/tinacms) - your feedback and contributions are welcome!
You can check out [Tina GitHub repository](https://github.com/tinacms/tinacms) - your feedback and contributions are welcome!

## [Deploy on Vercel](https://tina.io/guides/tina-cloud/add-tinacms-to-existing-site/deployment/)
6 changes: 3 additions & 3 deletions examples/hugo-quickstart/themes/ananke/stackbit.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -106,13 +106,13 @@ models:
label: Youtube
- type: string
name: github
label: Github
label: GitHub
- type: string
name: gitlab
label: Gitlab
label: GitLab
- type: string
name: linkedin
label: Linkedin
label: LinkedIn
- type: string
name: mastodon
label: Mastodon
Expand Down
2 changes: 1 addition & 1 deletion examples/tina-self-hosted-demo/content/pages/about.md

Large diffs are not rendered by default.

2 changes: 1 addition & 1 deletion examples/tina-self-hosted-demo/tina/config.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -263,7 +263,7 @@ const config = defineStaticConfig({
},
{
type: 'string',
label: 'Github',
label: 'GitHub',
name: 'github',
},
],
Expand Down
2 changes: 1 addition & 1 deletion experimental-examples/kitchen-sink/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,6 @@ To learn more about Tina, take a look at the following resources:
- [Getting starter guide](https://tina.io/guides/tina-cloud/starter/overview/)


You can check out [Tina Github repository](https://github.com/tinacms/tinacms) - your feedback and contributions are welcome!
You can check out [Tina GitHub repository](https://github.com/tinacms/tinacms) - your feedback and contributions are welcome!

## [Deploy on Vercel](https://tina.io/guides/tina-cloud/add-tinacms-to-existing-site/deployment/)
2 changes: 1 addition & 1 deletion experimental-examples/tina-cloud-starter/.tina/config.tsx
Original file line number Diff line number Diff line change
Expand Up @@ -247,7 +247,7 @@ const config = defineConfig({
},
{
type: 'string',
label: 'Github',
label: 'GitHub',
name: 'github',
},
],
Expand Down

Large diffs are not rendered by default.

Original file line number Diff line number Diff line change
Expand Up @@ -442,7 +442,7 @@ export class BuildCommand extends BaseCommand {
bar.tick({
prog: '❌',
})
let errorMessage = `The local GraphQL schema doesn't match the remote GraphQL schema. Please push up your changes to Github to update your remote GraphQL schema.`
let errorMessage = `The local GraphQL schema doesn't match the remote GraphQL schema. Please push up your changes to GitHub to update your remote GraphQL schema.`
if (config?.branch) {
errorMessage += `\n\nAdditional info: Branch: ${config.branch}, Client ID: ${config.clientId} `
}
Expand Down
4 changes: 2 additions & 2 deletions packages/@tinacms/cli/src/next/commands/dev-command/index.ts
Original file line number Diff line number Diff line change
Expand Up @@ -308,7 +308,7 @@ export class DevCommand extends BaseCommand {
* editing in their IDE or Tina pushing the update via the Filesystem bridge. It's a simple
* enough update that it's fine that when Tina pushes a change, we go and push that same
* thing back through the database, and Tina Cloud does the same thing when it receives
* a push from Github.
* a push from GitHub.
*/
chokidar
.watch(collectionContentFiles)
Expand Down Expand Up @@ -355,7 +355,7 @@ export class DevCommand extends BaseCommand {
* editing in their IDE or Tina pushing the update via the Filesystem bridge. It's a simple
* enough update that it's fine that when Tina pushes a change, we go and push that same
* thing back through the database, and Tina Cloud does the same thing when it receives
* a push from Github.
* a push from GitHub.
*/
chokidar
.watch(configManager.userQueriesAndFragmentsGlob)
Expand Down
14 changes: 7 additions & 7 deletions packages/@tinacms/graphql/src/database/README.md
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
The data layer currently has a lot of moving parts, the idea is that the Database class handles business operations, delegating down to the bridge/store for low-level functionality
The data layer currently has a lot of moving parts, the idea is that the Database class handles business operations, delegating down to the bridge/store for low-level functionality.

## The "bridge"

A bridge can be thought of as a way to get content from the ultimate source of truth into the content API.
This effectively comes in 2 forms, Github and Filesystem.
This effectively comes in 2 forms, GitHub and Filesystem.

The key differences between Github and Filesytem
are that Github doesn't support "building" the schema and every form save results in a Github commit.
The key differences between GitHub and Filesytem
are that GitHub doesn't support "building" the schema and every form save results in a GitHub commit.

The reason schema building isn't supported for the Github bridge is because that would required us to build on
The reason schema building isn't supported for the GitHub bridge is because that would required us to build on
every GraphQL request. Instead, we check the schema into source control, the schema was built by the developer
locally using the Fileystem bridge.

> When we get complete data store support, we can build the schema whenever we get a webhook from Github, this would allow our users to remove the `.tina/__generated__` files from source control if they wish to.
> When we get complete data store support, we can build the schema whenever we get a webhook from GitHub, this would allow our users to remove the `.tina/__generated__` files from source control if they wish to.
## The "store"

Expand All @@ -26,7 +26,7 @@ repo.

These indicate that the store can hold onto data by itself instead of sending it straight over to the bridge.
Seeding ideally happens whenever bridge data changes. For local setups, it currently only happens when the CLI
is started, for Github - I believe we'll want it to happen whenever we get a webhook from the Github API.
is started, for GitHub - I believe we'll want it to happen whenever we get a webhook from the GitHub API.

Generally these 2 concepts go hand-in-hand. They're separate so our tests can "seed" the data into memory
but otherwise behave like a non-data "stores", see [here](https://github.com/tinacms/tinacms/blob/main/packages/%40tinacms/graphql/src/spec/forestry-sample/requests.spec.ts#L20-L27).
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ import type { Bridge } from './index'
/**
* This is the bridge from whatever datasource we need for I/O.
* The basic example here is for the filesystem, one is needed
* for Github has well.
* for GitHub has well.
*/
export class FilesystemBridge implements Bridge {
public rootPath: string
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -487,7 +487,7 @@ const BranchSelector = ({
toolbarItems={[
branch.githubPullRequestUrl && {
name: 'github-pr',
label: 'View in Github',
label: 'View in GitHub',
Icon: (
<BiLinkExternal className="w-5 h-auto text-blue-500 opacity-70" />
),
Expand Down

0 comments on commit 56cbd96

Please sign in to comment.