Skip to content

Fix 'git' brand letter casing #615

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Fix 'git' brand letter casing #615

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions docs/specs/devcontainer-features-distribution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,9 +15,9 @@ Goals include:

## Source code

Features source code is stored in a git repository.
Features source code is stored in a Git repository.

For ease of authorship and maintenance, [1..n] features can share a single git repository. This set of features is referred to as a "collection," and will share the same [`devcontainer-collection.json`](#devcontainer-collection.json) file and "namespace" (eg. `<owner>/<repo>`).
For ease of authorship and maintenance, [1..n] features can share a single Git repository. This set of features is referred to as a "collection," and will share the same [`devcontainer-collection.json`](#devcontainer-collection.json) file and "namespace" (eg. `<owner>/<repo>`).

Source code for the set follows the example file structure below:

Expand Down Expand Up @@ -117,7 +117,7 @@ done

```

The "namespace" is the globally identifiable name for the collection of Features. (eg: `owner/repo` for the source code's git repository).
The "namespace" is the globally identifiable name for the collection of Features. (eg: `owner/repo` for the source code's Git repository).

The auto-generated `devcontainer-collection.json` is pushed to the registry with the same `namespace` as above and no accompanying `feature` name. The collection file is always tagged as `latest`.

Expand Down
2 changes: 1 addition & 1 deletion docs/specs/devcontainer-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,4 +283,4 @@ Each entry in the `object` will be run in parallel during that lifecycle step.

#### **Project Workspace Folder**

The **project workspace folder** is where an implementing tool should begin to search for `devcontainer.json` files. If the target project on disk is using git, the **project workspace folder** is typically the root of the git repository.
The **project workspace folder** is where an implementing tool should begin to search for `devcontainer.json` files. If the target project on disk is using Git, the **project workspace folder** is typically the root of the Git repository.
8 changes: 4 additions & 4 deletions docs/specs/devcontainer-templates-distribution.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,11 @@ Goals include:

## Source code

A Template's source code is stored in a git repository.
A Template's source code is stored in a Git repository.

For ease of authorship and maintenance, [1..n] Templates can share a single git repository. This set of Templates is referred to as a "collection," and will share the same [`devcontainer-collection.json`](#devcontainer-collection.json) file and "namespace" (eg. `<owner>/<repo>`).
For ease of authorship and maintenance, [1..n] Templates can share a single Git repository. This set of Templates is referred to as a "collection," and will share the same [`devcontainer-collection.json`](#devcontainer-collection.json) file and "namespace" (eg. `<owner>/<repo>`).

> **Note:** Templates and [Features](./devcontainer-features.md) should be placed in different git repositories.
> **Note:** Templates and [Features](./devcontainer-features.md) should be placed in different Git repositories.

Source code for a set of Templates follows the example file structure below:

Expand Down Expand Up @@ -114,7 +114,7 @@ done

```

The "namespace" is the globally identifiable name for the collection of Templates. (eg: `owner/repo` for the source code's git repository).
The "namespace" is the globally identifiable name for the collection of Templates. (eg: `owner/repo` for the source code's Git repository).

The auto-generated `devcontainer-collection.json` is pushed to the registry with the same `namespace` as above and no accompanying `template` name. The collection file is always tagged as `latest`.

Expand Down