1
0
mirror of synced 2026-01-09 06:03:09 -05:00

Merge branch 'main' into repo-sync

This commit is contained in:
Octomerger Bot
2021-09-11 14:02:35 -04:00
committed by GitHub
77 changed files with 189 additions and 183 deletions

View File

@@ -4270,6 +4270,19 @@ qualified).
The Ref may be specified by its global node ID or by the
repository nameWithOwner and branch name.
### Examples
Specify a branch using a global node ID:
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }
Specify a branch using nameWithOwner and branch name:
{
"nameWithOwner": "github/graphql-client",
"branchName": "main"
}
"""
input CommittableBranch {
"""
@@ -11758,7 +11771,7 @@ slash-prefixed.
`path` values must be unique across all `additions` and `deletions`
provided. Any duplication will result in a validation error.
## Encoding
### Encoding
File contents must be provided in full for each `FileAddition`.
@@ -11778,7 +11791,7 @@ and ensuring that all files in a repository use a consistent
line-ending convention (`\n` or `\r\n`), and that all files end
with a newline.
## Modeling file changes
### Modeling file changes
Each of the the five types of conceptual changes that can be made in a
git commit can be described using the `FileChanges` type as follows:
@@ -16537,7 +16550,7 @@ type Mutation {
branch and also updates that branch to point to the new commit.
It can be thought of as similar to `git commit`.
## Locating a Branch
### Locating a Branch
Commits are appended to a `branch` of type `Ref`.
This must refer to a git branch (i.e. the fully qualified path must
@@ -16547,7 +16560,7 @@ type Mutation {
ID or by passing both of `repositoryNameWithOwner` and `refName`. For
more details see the documentation for `CommittableBranch`.
## Describing Changes
### Describing Changes
`fileChanges` are specified as a `FilesChanges` object describing
`FileAdditions` and `FileDeletions`.
@@ -16555,7 +16568,7 @@ type Mutation {
Please see the documentation for `FileChanges` for more information on
how to use this argument to describe any set of file changes.
## Authorship
### Authorship
Similar to the web commit interface, this mutation does not support
specifying the author or committer of the commit and will not add
@@ -16569,7 +16582,7 @@ type Mutation {
If you need full control over author and committer information, please
use the Git Database REST API instead.
## Commit Signing
### Commit Signing
Commits made using this mutation are automatically signed by GitHub if
supported and will be marked as verified in the user interface.

View File

@@ -4472,6 +4472,19 @@ qualified).
The Ref may be specified by its global node ID or by the
repository nameWithOwner and branch name.
### Examples
Specify a branch using a global node ID:
{ "id": "MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=" }
Specify a branch using nameWithOwner and branch name:
{
"nameWithOwner": "github/graphql-client",
"branchName": "main"
}
"""
input CommittableBranch {
"""
@@ -12496,7 +12509,7 @@ slash-prefixed.
`path` values must be unique across all `additions` and `deletions`
provided. Any duplication will result in a validation error.
## Encoding
### Encoding
File contents must be provided in full for each `FileAddition`.
@@ -12516,7 +12529,7 @@ and ensuring that all files in a repository use a consistent
line-ending convention (`\n` or `\r\n`), and that all files end
with a newline.
## Modeling file changes
### Modeling file changes
Each of the the five types of conceptual changes that can be made in a
git commit can be described using the `FileChanges` type as follows:
@@ -17854,7 +17867,7 @@ type Mutation {
branch and also updates that branch to point to the new commit.
It can be thought of as similar to `git commit`.
## Locating a Branch
### Locating a Branch
Commits are appended to a `branch` of type `Ref`.
This must refer to a git branch (i.e. the fully qualified path must
@@ -17864,7 +17877,7 @@ type Mutation {
ID or by passing both of `repositoryNameWithOwner` and `refName`. For
more details see the documentation for `CommittableBranch`.
## Describing Changes
### Describing Changes
`fileChanges` are specified as a `FilesChanges` object describing
`FileAdditions` and `FileDeletions`.
@@ -17872,7 +17885,7 @@ type Mutation {
Please see the documentation for `FileChanges` for more information on
how to use this argument to describe any set of file changes.
## Authorship
### Authorship
Similar to the web commit interface, this mutation does not support
specifying the author or committer of the commit and will not add
@@ -17886,7 +17899,7 @@ type Mutation {
If you need full control over author and committer information, please
use the Git Database REST API instead.
## Commit Signing
### Commit Signing
Commits made using this mutation are automatically signed by GitHub if
supported and will be marked as verified in the user interface.

File diff suppressed because one or more lines are too long

View File

@@ -2002,7 +2002,7 @@
"kind": "mutations",
"id": "createcommitonbranch",
"href": "/graphql/reference/mutations#createcommitonbranch",
"description": "<p>Appends a commit to the given branch as the authenticated user.</p>\n<p>This mutation creates a commit whose parent is the HEAD of the provided\nbranch and also updates that branch to point to the new commit.\nIt can be thought of as similar to <code>git commit</code>.</p>\n<h2 id=\"locating-a-branch\"><a href=\"#locating-a-branch\">Locating a Branch</a></h2>\n<p>Commits are appended to a <code>branch</code> of type <code>Ref</code>.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with <code>refs/heads/</code>, although including this prefix is optional.</p>\n<p>Callers may specify the <code>branch</code> to commit to either by its global node\nID or by passing both of <code>repositoryNameWithOwner</code> and <code>refName</code>. For\nmore details see the documentation for <code>CommittableBranch</code>.</p>\n<h2 id=\"describing-changes\"><a href=\"#describing-changes\">Describing Changes</a></h2>\n<p><code>fileChanges</code> are specified as a <code>FilesChanges</code> object describing\n<code>FileAdditions</code> and <code>FileDeletions</code>.</p>\n<p>Please see the documentation for <code>FileChanges</code> for more information on\nhow to use this argument to describe any set of file changes.</p>\n<h2 id=\"authorship\"><a href=\"#authorship\">Authorship</a></h2>\n<p>Similar to the web commit interface, this mutation does not support\nspecifying the author or committer of the commit and will not add\nsupport for this in the future.</p>\n<p>A commit created by a successful execution of this mutation will be\nauthored by the owner of the credential which authenticates the API\nrequest. The committer will be identical to that of commits authored\nusing the web interface.</p>\n<p>If you need full control over author and committer information, please\nuse the Git Database REST API instead.</p>\n<h2 id=\"commit-signing\"><a href=\"#commit-signing\">Commit Signing</a></h2>\n<p>Commits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.</p>",
"description": "<p>Appends a commit to the given branch as the authenticated user.</p>\n<p>This mutation creates a commit whose parent is the HEAD of the provided\nbranch and also updates that branch to point to the new commit.\nIt can be thought of as similar to <code>git commit</code>.</p>\n<h3 id=\"locating-a-branch\"><a href=\"#locating-a-branch\">Locating a Branch</a></h3>\n<p>Commits are appended to a <code>branch</code> of type <code>Ref</code>.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with <code>refs/heads/</code>, although including this prefix is optional.</p>\n<p>Callers may specify the <code>branch</code> to commit to either by its global node\nID or by passing both of <code>repositoryNameWithOwner</code> and <code>refName</code>. For\nmore details see the documentation for <code>CommittableBranch</code>.</p>\n<h3 id=\"describing-changes\"><a href=\"#describing-changes\">Describing Changes</a></h3>\n<p><code>fileChanges</code> are specified as a <code>FilesChanges</code> object describing\n<code>FileAdditions</code> and <code>FileDeletions</code>.</p>\n<p>Please see the documentation for <code>FileChanges</code> for more information on\nhow to use this argument to describe any set of file changes.</p>\n<h3 id=\"authorship\"><a href=\"#authorship\">Authorship</a></h3>\n<p>Similar to the web commit interface, this mutation does not support\nspecifying the author or committer of the commit and will not add\nsupport for this in the future.</p>\n<p>A commit created by a successful execution of this mutation will be\nauthored by the owner of the credential which authenticates the API\nrequest. The committer will be identical to that of commits authored\nusing the web interface.</p>\n<p>If you need full control over author and committer information, please\nuse the Git Database REST API instead.</p>\n<h3 id=\"commit-signing\"><a href=\"#commit-signing\">Commit Signing</a></h3>\n<p>Commits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.</p>",
"inputFields": [
{
"name": "input",
@@ -71467,7 +71467,7 @@
"kind": "inputObjects",
"id": "committablebranch",
"href": "/graphql/reference/input-objects#committablebranch",
"description": "<p>A git ref for a commit to be appended to.</p>\n<p>The ref must be a branch, i.e. its fully qualified name must start\nwith <code>refs/heads/</code> (although the input is not required to be fully\nqualified).</p>\n<p>The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.</p>",
"description": "<p>A git ref for a commit to be appended to.</p>\n<p>The ref must be a branch, i.e. its fully qualified name must start\nwith <code>refs/heads/</code> (although the input is not required to be fully\nqualified).</p>\n<p>The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.</p>\n<h3 id=\"examples\"><a href=\"#examples\">Examples</a></h3>\n<p>Specify a branch using a global node ID:</p>\n<pre><code>{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\n</code></pre>\n<p>Specify a branch using nameWithOwner and branch name:</p>\n<pre><code>{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\n</code></pre>",
"inputFields": [
{
"name": "branchName",
@@ -73956,7 +73956,7 @@
"kind": "inputObjects",
"id": "filechanges",
"href": "/graphql/reference/input-objects#filechanges",
"description": "<p>A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file <code>additions</code> and zero or more\nfile <code>deletions</code>.</p>\n<p>Both fields are optional; omitting both will produce a commit with no\nfile changes.</p>\n<p><code>deletions</code> and <code>additions</code> describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n<code>/</code>. The root of a git tree is an empty string, so paths are not\nslash-prefixed.</p>\n<p><code>path</code> values must be unique across all <code>additions</code> and <code>deletions</code>\nprovided. Any duplication will result in a validation error.</p>\n<h2 id=\"encoding\"><a href=\"#encoding\">Encoding</a></h2>\n<p>File contents must be provided in full for each <code>FileAddition</code>.</p>\n<p>The <code>contents</code> of a <code>FileAddition</code> must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.</p>\n<p>The encoded contents may be binary.</p>\n<p>For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (<code>\\n</code> or <code>\\r\\n</code>), and that all files end\nwith a newline.</p>\n<h2 id=\"modeling-file-changes\"><a href=\"#modeling-file-changes\">Modeling file changes</a></h2>\n<p>Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the <code>FileChanges</code> type as follows:</p>\n<ol>\n<li>\n<p>New file addition: create file <code>hello world\\n</code> at path <code>docs/README.txt</code>:</p>\n<p> {\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}</p>\n</li>\n<li>\n<p>Existing file modification: change existing <code>docs/README.txt</code> to have new\ncontent <code>new content here\\n</code>:</p>\n<pre><code>{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>Existing file deletion: remove existing file <code>docs/README.txt</code>.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with no changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to the same content at\n<code>newdocs/README.txt</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"hello world\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to a file at path\n<code>newdocs/README.txt</code> with content <code>new contents\\n</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"new contents\\n\")\n }\n ]\n}.\n</code></pre>\n</li>\n</ol>",
"description": "<p>A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file <code>additions</code> and zero or more\nfile <code>deletions</code>.</p>\n<p>Both fields are optional; omitting both will produce a commit with no\nfile changes.</p>\n<p><code>deletions</code> and <code>additions</code> describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n<code>/</code>. The root of a git tree is an empty string, so paths are not\nslash-prefixed.</p>\n<p><code>path</code> values must be unique across all <code>additions</code> and <code>deletions</code>\nprovided. Any duplication will result in a validation error.</p>\n<h3 id=\"encoding\"><a href=\"#encoding\">Encoding</a></h3>\n<p>File contents must be provided in full for each <code>FileAddition</code>.</p>\n<p>The <code>contents</code> of a <code>FileAddition</code> must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.</p>\n<p>The encoded contents may be binary.</p>\n<p>For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (<code>\\n</code> or <code>\\r\\n</code>), and that all files end\nwith a newline.</p>\n<h3 id=\"modeling-file-changes\"><a href=\"#modeling-file-changes\">Modeling file changes</a></h3>\n<p>Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the <code>FileChanges</code> type as follows:</p>\n<ol>\n<li>\n<p>New file addition: create file <code>hello world\\n</code> at path <code>docs/README.txt</code>:</p>\n<p> {\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}</p>\n</li>\n<li>\n<p>Existing file modification: change existing <code>docs/README.txt</code> to have new\ncontent <code>new content here\\n</code>:</p>\n<pre><code>{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>Existing file deletion: remove existing file <code>docs/README.txt</code>.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with no changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to the same content at\n<code>newdocs/README.txt</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"hello world\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to a file at path\n<code>newdocs/README.txt</code> with content <code>new contents\\n</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"new contents\\n\")\n }\n ]\n}.\n</code></pre>\n</li>\n</ol>",
"inputFields": [
{
"name": "additions",

View File

@@ -1545,7 +1545,7 @@
"kind": "mutations",
"id": "createcommitonbranch",
"href": "/graphql/reference/mutations#createcommitonbranch",
"description": "<p>Appends a commit to the given branch as the authenticated user.</p>\n<p>This mutation creates a commit whose parent is the HEAD of the provided\nbranch and also updates that branch to point to the new commit.\nIt can be thought of as similar to <code>git commit</code>.</p>\n<h2 id=\"locating-a-branch\"><a href=\"#locating-a-branch\">Locating a Branch</a></h2>\n<p>Commits are appended to a <code>branch</code> of type <code>Ref</code>.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with <code>refs/heads/</code>, although including this prefix is optional.</p>\n<p>Callers may specify the <code>branch</code> to commit to either by its global node\nID or by passing both of <code>repositoryNameWithOwner</code> and <code>refName</code>. For\nmore details see the documentation for <code>CommittableBranch</code>.</p>\n<h2 id=\"describing-changes\"><a href=\"#describing-changes\">Describing Changes</a></h2>\n<p><code>fileChanges</code> are specified as a <code>FilesChanges</code> object describing\n<code>FileAdditions</code> and <code>FileDeletions</code>.</p>\n<p>Please see the documentation for <code>FileChanges</code> for more information on\nhow to use this argument to describe any set of file changes.</p>\n<h2 id=\"authorship\"><a href=\"#authorship\">Authorship</a></h2>\n<p>Similar to the web commit interface, this mutation does not support\nspecifying the author or committer of the commit and will not add\nsupport for this in the future.</p>\n<p>A commit created by a successful execution of this mutation will be\nauthored by the owner of the credential which authenticates the API\nrequest. The committer will be identical to that of commits authored\nusing the web interface.</p>\n<p>If you need full control over author and committer information, please\nuse the Git Database REST API instead.</p>\n<h2 id=\"commit-signing\"><a href=\"#commit-signing\">Commit Signing</a></h2>\n<p>Commits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.</p>",
"description": "<p>Appends a commit to the given branch as the authenticated user.</p>\n<p>This mutation creates a commit whose parent is the HEAD of the provided\nbranch and also updates that branch to point to the new commit.\nIt can be thought of as similar to <code>git commit</code>.</p>\n<h3 id=\"locating-a-branch\"><a href=\"#locating-a-branch\">Locating a Branch</a></h3>\n<p>Commits are appended to a <code>branch</code> of type <code>Ref</code>.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with <code>refs/heads/</code>, although including this prefix is optional.</p>\n<p>Callers may specify the <code>branch</code> to commit to either by its global node\nID or by passing both of <code>repositoryNameWithOwner</code> and <code>refName</code>. For\nmore details see the documentation for <code>CommittableBranch</code>.</p>\n<h3 id=\"describing-changes\"><a href=\"#describing-changes\">Describing Changes</a></h3>\n<p><code>fileChanges</code> are specified as a <code>FilesChanges</code> object describing\n<code>FileAdditions</code> and <code>FileDeletions</code>.</p>\n<p>Please see the documentation for <code>FileChanges</code> for more information on\nhow to use this argument to describe any set of file changes.</p>\n<h3 id=\"authorship\"><a href=\"#authorship\">Authorship</a></h3>\n<p>Similar to the web commit interface, this mutation does not support\nspecifying the author or committer of the commit and will not add\nsupport for this in the future.</p>\n<p>A commit created by a successful execution of this mutation will be\nauthored by the owner of the credential which authenticates the API\nrequest. The committer will be identical to that of commits authored\nusing the web interface.</p>\n<p>If you need full control over author and committer information, please\nuse the Git Database REST API instead.</p>\n<h3 id=\"commit-signing\"><a href=\"#commit-signing\">Commit Signing</a></h3>\n<p>Commits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.</p>",
"inputFields": [
{
"name": "input",
@@ -64290,7 +64290,7 @@
"kind": "inputObjects",
"id": "committablebranch",
"href": "/graphql/reference/input-objects#committablebranch",
"description": "<p>A git ref for a commit to be appended to.</p>\n<p>The ref must be a branch, i.e. its fully qualified name must start\nwith <code>refs/heads/</code> (although the input is not required to be fully\nqualified).</p>\n<p>The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.</p>",
"description": "<p>A git ref for a commit to be appended to.</p>\n<p>The ref must be a branch, i.e. its fully qualified name must start\nwith <code>refs/heads/</code> (although the input is not required to be fully\nqualified).</p>\n<p>The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.</p>\n<h3 id=\"examples\"><a href=\"#examples\">Examples</a></h3>\n<p>Specify a branch using a global node ID:</p>\n<pre><code>{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\n</code></pre>\n<p>Specify a branch using nameWithOwner and branch name:</p>\n<pre><code>{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\n</code></pre>",
"inputFields": [
{
"name": "branchName",
@@ -66568,7 +66568,7 @@
"kind": "inputObjects",
"id": "filechanges",
"href": "/graphql/reference/input-objects#filechanges",
"description": "<p>A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file <code>additions</code> and zero or more\nfile <code>deletions</code>.</p>\n<p>Both fields are optional; omitting both will produce a commit with no\nfile changes.</p>\n<p><code>deletions</code> and <code>additions</code> describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n<code>/</code>. The root of a git tree is an empty string, so paths are not\nslash-prefixed.</p>\n<p><code>path</code> values must be unique across all <code>additions</code> and <code>deletions</code>\nprovided. Any duplication will result in a validation error.</p>\n<h2 id=\"encoding\"><a href=\"#encoding\">Encoding</a></h2>\n<p>File contents must be provided in full for each <code>FileAddition</code>.</p>\n<p>The <code>contents</code> of a <code>FileAddition</code> must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.</p>\n<p>The encoded contents may be binary.</p>\n<p>For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (<code>\\n</code> or <code>\\r\\n</code>), and that all files end\nwith a newline.</p>\n<h2 id=\"modeling-file-changes\"><a href=\"#modeling-file-changes\">Modeling file changes</a></h2>\n<p>Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the <code>FileChanges</code> type as follows:</p>\n<ol>\n<li>\n<p>New file addition: create file <code>hello world\\n</code> at path <code>docs/README.txt</code>:</p>\n<p> {\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}</p>\n</li>\n<li>\n<p>Existing file modification: change existing <code>docs/README.txt</code> to have new\ncontent <code>new content here\\n</code>:</p>\n<pre><code>{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>Existing file deletion: remove existing file <code>docs/README.txt</code>.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with no changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to the same content at\n<code>newdocs/README.txt</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"hello world\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to a file at path\n<code>newdocs/README.txt</code> with content <code>new contents\\n</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"new contents\\n\")\n }\n ]\n}.\n</code></pre>\n</li>\n</ol>",
"description": "<p>A description of a set of changes to a file tree to be made as part of\na git commit, modeled as zero or more file <code>additions</code> and zero or more\nfile <code>deletions</code>.</p>\n<p>Both fields are optional; omitting both will produce a commit with no\nfile changes.</p>\n<p><code>deletions</code> and <code>additions</code> describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n<code>/</code>. The root of a git tree is an empty string, so paths are not\nslash-prefixed.</p>\n<p><code>path</code> values must be unique across all <code>additions</code> and <code>deletions</code>\nprovided. Any duplication will result in a validation error.</p>\n<h3 id=\"encoding\"><a href=\"#encoding\">Encoding</a></h3>\n<p>File contents must be provided in full for each <code>FileAddition</code>.</p>\n<p>The <code>contents</code> of a <code>FileAddition</code> must be encoded using RFC 4648\ncompliant base64, i.e. correct padding is required and no characters\noutside the standard alphabet may be used. Invalid base64\nencoding will be rejected with a validation error.</p>\n<p>The encoded contents may be binary.</p>\n<p>For text files, no assumptions are made about the character encoding of\nthe file contents (after base64 decoding). No charset transcoding or\nline-ending normalization will be performed; it is the client's\nresponsibility to manage the character encoding of files they provide.\nHowever, for maximum compatibility we recommend using UTF-8 encoding\nand ensuring that all files in a repository use a consistent\nline-ending convention (<code>\\n</code> or <code>\\r\\n</code>), and that all files end\nwith a newline.</p>\n<h3 id=\"modeling-file-changes\"><a href=\"#modeling-file-changes\">Modeling file changes</a></h3>\n<p>Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the <code>FileChanges</code> type as follows:</p>\n<ol>\n<li>\n<p>New file addition: create file <code>hello world\\n</code> at path <code>docs/README.txt</code>:</p>\n<p> {\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}</p>\n</li>\n<li>\n<p>Existing file modification: change existing <code>docs/README.txt</code> to have new\ncontent <code>new content here\\n</code>:</p>\n<pre><code>{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>Existing file deletion: remove existing file <code>docs/README.txt</code>.\nNote that the path is required to exist -- specifying a\npath that does not exist on the given branch will abort the\ncommit and return an error.</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with no changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to the same content at\n<code>newdocs/README.txt</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"hello world\\n\")\n }\n ]\n}\n</code></pre>\n</li>\n<li>\n<p>File rename with changes: rename <code>docs/README.txt</code> with\nprevious content <code>hello world\\n</code> to a file at path\n<code>newdocs/README.txt</code> with content <code>new contents\\n</code>:</p>\n<pre><code>{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\",\n }\n ],\n \"additions\" [\n {\n \"path\": \"newdocs/README.txt\",\n \"contents\": base64encode(\"new contents\\n\")\n }\n ]\n}.\n</code></pre>\n</li>\n</ol>",
"inputFields": [
{
"name": "additions",

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:8e573b9b303ea50d179a892e32c1ff735471894324bc5289b423894f852cd7ba
size 506772
oid sha256:b8a23d65ade8b0d5bf84f27eb34dbe517df1959a4fbcd3ee3cfd531790d8cf30
size 506858

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:6219435ad314d2150901dbaf06173505ceabd32e2a2af1442ed68467d8a255a0
size 803154
oid sha256:97cfcaed2bac25875e2ef326393fc89663d1ac73e18ccdba7f9b9e548b4f02d0
size 802579

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:30493d1c7d8e2d7d5589456d89cd8e67f4056028fe5c0654d273d1941763b228
size 469518
oid sha256:d9607bacae15d9619d3220e1857f56aea63068fe04f1c0fa488dbae51982e2c2
size 469932

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c2f0f524ef2e7370307ae08180488d86ee524297c0744244df71602ba2a71ce9
size 2079398
oid sha256:7360382fceb98d0a10ed942324d548a11560eb3a9397d980810afee3738d8e74
size 2079383

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:cd04827a8f797d15d59cd2e8bdc030d788e67d7e6e90447d89436482cca2c68f
size 430415
oid sha256:f274a97157c60b9ffe7d47b5661954accec65185c35e547f3734f79482bc526b
size 430406

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:8a05e5eeb962d808f64625b568ef4c009c1e70c86eda63e69fd43ea533e8406c
size 1682023
oid sha256:8661e8cbebea488a337223173e74f548355155655ee043d4e43952c0846a1f29
size 1681975

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:564458609fc1d43350163bc6b2a8be5d3a3b3598b722affd3275e595fb5251b1
size 280276
oid sha256:a4acf3ff7592e3233776a29688735f27558af79d4d1a906c70fea45f327a3ee9
size 280300

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:521dc77045655f318bc95242bf7f70cb45fe469b287b0cb77d13b1305f9c2552
size 1067220
oid sha256:c8cfccb0e0613bc5018f6e89e60086894d1f80ade2aec06e2b75bcbcb8e95035
size 1067362

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:6bf1357233a85d221e324f084a2a77726d13b9209f77db169efc218a331c93b2
size 528747
oid sha256:627e8a160e7985d3730511da017fa1ec856d7c2487e6ebb499e4eb9e6083bfff
size 529093

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:3600ba9c7c6a7428d697adbbbfd920aff30cf2a3da00d5cea19de8df2da0a49a
size 2796732
oid sha256:cd960bf68475270e95396dd551e51d9615954d204c4b0a43004a6992d3bd9fdf
size 2799274

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:e657b9ff71083553264741a770f7a604da54affb0ed533befb9cc638bd8d9f01
size 443564
oid sha256:f94aae874d081161488ab3540417f78b1a8a4eced26ad872248bf324aa97470a
size 443528

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2ff3f4ac321a18406146a2eb99c1831673aa7a68f55161c1bbbb21ef0d591f7f
size 1852851
oid sha256:c44383a9336ec3d4a32f5544674152655d9e741740abc8188746d5cba3b7c8f8
size 1851946

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:0bab8ff37d13b4f7ea841e9c13850d951239fbe1cb67b2bf9e29478142c2d0fb
size 524675
oid sha256:512d32193931cee6536f9f798910c47f57f4ea3da7049a4575ef9d46d17fd4dd
size 524511

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:abc88abdc76c4c101c0480135b089c13ab372fa16ae7ca83b8547c3456bf6d22
size 834208
oid sha256:64ae93f070762044dc1bc4022988b9b818b7a72a82c4317928ab202230640a6d
size 833971

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:00edafe7e8ee4049ed74358977c95eca2792a87253174465c883e3a7afe39847
size 490319
oid sha256:a68acf5abe7b9683d9384795ffd9f03fddc02ae20588cfbb0b90887307b36142
size 490659

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:e3723c3ba34e0f3485df4cb73137ae8e388f99315543b17ba170f0ba2aecf182
size 2179543
oid sha256:78e4f1be335620984806dfe9391d3da96efdc3b13f6c0c8dfe6d06fd437e25f9
size 2180727

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:51af79360af80431f5de08bad4adafba6c0ab3e7e89f59de738e109c9a56703f
size 450935
oid sha256:16d25d4098d19a38343a18d08d52f1b8ae3f47971318167c7e7891626659dbb4
size 450569

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:56d861a81671bb5bfec323e04cb3529c950c873f01d4a6d0a8c157a25025e231
size 1756017
oid sha256:72bb171b3c146b036ad8aef9f1b796853f886fe85ae706eddf00e3edef8265d4
size 1753782

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:f85ad30577cf84fd71a07f7176f2c026e82517b403d3c8592d218710a97a6bda
size 278112
oid sha256:fed449d421e1dd930eac932b8d1b2c7d25719877e91ab3a75b2ccfe128a443e2
size 278182

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:b71a1bfae0bd3a4b5e4db9abde8bc5e95d5cb1fb2db148933bda573ed261ecb2
size 1056747
oid sha256:c907e96f7361a7dd4a815eee24d81ef977c4619fb92170e433b593b5e7a92ec4
size 1055220

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:438c3d1375053302014b96409b64c3f2cb9b78b4134ef9bf6a3454dba849d47b
size 550599
oid sha256:51cb3bfbbb99ebe0431150cc68f82bcd343f81986a47fd7df92693ae4e717e68
size 550278

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:db93ccb8e0a7a4bf64448923f6ad65fe71244aa23d355ec05c1dcc2b0708a44d
size 2913265
oid sha256:e4bcc3a4e1cf302e5dafce0787c8e1ae51cba61bd8f7cb55a4e09c53c9e19525
size 2912068

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:4c2067427c010dc2cd9f9a28bfb974e60d3c4746af570fff7fb814690cb040b9
size 464758
oid sha256:bcdea2ff8698a4af486bd325484de09c11a1882ed80180402b42060bfbac40de
size 464635

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:4701b60877205703dad31997fd65c5d0bae7beca3a76007bf84ec1b996302e21
size 1937081
oid sha256:e086fef41e7d4f4de6707a87e62e361d4ac94331041c8734f0faf5859d1f1c60
size 1936807

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:d072a04a7c7b302c7c048fc7f270aeae0f89c65a3a11ee49f970bc470635946c
size 534123
oid sha256:0474fa425214773e38a16729cfe9ece411ba4a7b73e6e3fd4e5579580a82cee9
size 534107

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:9f6f6e0c045269d2a2f9734698991eb6b844d4c9be2a18833de59d1dfb99d3c2
size 846481
oid sha256:627fa5b73f918132f175573fc7cdbfd9470783c70314a357fed219bc3a59ecee
size 846398

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:62feeefea82fdbf03d5cbe609facd9f517bfc4d508eb2ebf9a569f012dc18c0b
size 497307
oid sha256:bbc05f25acb263bd62a8152d7d486cfb7fb2c77bad7478413e7277f3872cc178
size 497550

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:a0915ea247bfa273bcbaa604d4b170ba178caf655ea0a9f71fc0c98de03ea4a1
size 2221255
oid sha256:d9565232b5029f0f6fab32d7a0da0e3f646cd3aa05951657659d1af96e138938
size 2222164

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:1f4fcfab968d7f0492696c95f6a911382868dc24788988c92beb4810b434f62a
size 459236
oid sha256:040a66d007dcc8f9e0d7f3997a1721f8eceeb7f0312367b922d8461c64238274
size 459254

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:957c3b5b1ece2d7ddd2fcae6defc973d57e277c445b5fc5d745a935fccdd3223
size 1790253
oid sha256:840af55ac9461e36a7ba2b0bc64771a57f3c55ba10303144080d81b8d12de368
size 1791912

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2362a124fa892ab1ce676e6fe2517b00348334a9b3fe891c10acbde3ad3b049a
size 278636
oid sha256:29ac3213c4a1fd46219af30403ff97ba072ce0ec3a9d5da67c85f1cf14592cac
size 278416

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:e07e6cd207dd4c34783cde4d535065237d10f6ed7e4d273bad4545f14946369d
size 1056874
oid sha256:5fd4d8a7651f30aec6573b73d98cd2532378df0e7c82a8e6c4acbd7921425a85
size 1057041

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:3b9db2b883fadc224340a7328865d1c8a4f053b56eb15fac3f64a326433f0839
size 558795
oid sha256:b0712526d98d245f0f9f4f0c237510cd3df47d2483394f2db62bf814a3290086
size 559417

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:049850c83bab1ddff6b5d30a7588b5945d2ec2811d146bca880b7f7c6d482730
size 2963624
oid sha256:56f833bda536290c9284b0d49459faf20af94956ac7f680b187bf039ddd2b0d0
size 2968075

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:0cb0b0c2a2425ba83c6757496d28c8dfda3b913890bf8ba783237bf4ce2fe1dc
size 472253
oid sha256:45976e6bf7bd3fcc236dcd75229fc210a5ec27b95447fe5c1bd6e8e129ababaa
size 472643

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:db247e4c66c16cbfd5f8e25743b018644678069ba5132e16b088a9ba471acd6d
size 1972579
oid sha256:8f71cb0000d49fb00883d73bfe3224c44263c87286199671da9d5f004067f9f3
size 1974576

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:85e06a3865db594bec7857529c704a7a2445930c0956ce249ef275dde915e843
size 539898
oid sha256:3047d5a118f27afd9299e355f74339d15d6273c6130b401afd3d9e0980c51137
size 540010

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:596353ea4099c40e72bb7681c317d5547f65c5dc917933fef9b246f097d06da7
size 853895
oid sha256:a18c43fa7ddf247e4816f78f8a95474db1b70bfee371c494f2c78dcecda156f7
size 854128

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:ec9deaf60b4a4831af2e204a9d49a8f2d21eeab9d9e432fbfda997c32db2dee7
size 502183
oid sha256:037fdda0eb0ec258eb569e9f80c0b47684a9d1477f1ff671a72436cb12159474
size 501894

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2c4185626332a40002b95b8e9a955466e955497a94df175b1c726b39433eaab7
size 2246921
oid sha256:32856cb7a52385dea354a3d25e409dba01ccfac9a32db66fe7663e11a35b4dec
size 2244701

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c3c219ee7cf591973e752b835f994dff16770f00077142bfc0ac8e57ec934f62
size 467948
oid sha256:40c5ed5823e733003d1f967f20209853bb6dd0a1f9bdf8474e88599860d527f9
size 467726

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:05a3222bfcc9d5a6ac91cbdcf678926c3b8aa90aa605489fc94dd91d073f7973
size 1823300
oid sha256:eba670b5fbaa42adf13060f10d3fbe876f051128afda0e52ae0b6e8bc34eee12
size 1823212

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:e9f866e175862933261c3e5266ecbd16df4d8cdf9b236d2985b4729f027d22fd
size 278420
oid sha256:8e2198c1442295b2362adc899664e5c0c440523a4882b582aece8ebbc807df67
size 278467

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:cae58a2b2e8d412fb4a082e3c3b7511ac5d608f5e839f712403740650d8e8e44
size 1057401
oid sha256:4aed0bb798458c2c90163451eb13b0ba9e8225a065767edf345a209647eeeab0
size 1057188

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c7f05b589534e06cbe252dfbac9440628f8e3357812a2bed6975f71715dd23f6
size 564838
oid sha256:60a39826cca78566457407b55df14ef9076feeb28f4dd2f30aad079052dc5dbb
size 564837

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:e3a34af6aa4264f013347e08a9b81dae17f8208bd163e117fbf1dbf100dc241e
size 2997085
oid sha256:0f1b42ea356a85c0119dd493e7d1ad5c7ea2156b77962fdb1ff1ccd341f81ff0
size 2997747

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:85dd7901bb17e1483a7dfff3ef91ce85ff00030b1a298d3dba6805a688a3aee2
size 477347
oid sha256:140833b932ca508e7a12a00af3b867fd0ad919b90f14e69f73f6334c87e68bad
size 476882

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:291cc8bc769e53d90f3ea67c4aaaad5d7ca9c72b46dd38498ecc09c1d93ee0db
size 1997166
oid sha256:4f7e2963b65704ddd2bf9e942d6c0151fad900b82cb0b0cf319c722cbea167e5
size 1995196

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:b952f9daa4bf979a2d60df3aa745f5387945c5c6d269b74599e233721729f501
size 695647
oid sha256:d689f9abab6dc41f5d6aeea9341cf4179a3dcb017736e9e8cdb5b12b88f50d35
size 696239

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c3679192f4c0da80972e166e119b358fe1b14b98d43b8cf7b1f459a22a29a31b
size 947817
oid sha256:72ddcb930d526351e7f3e7e82f071e6bb4c843900c41f2d60a18f83b4dd51cdd
size 947664

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:9cc90cb49cd4297c00f0af23d5025b4256648603ffc0e1f7c9d00d296e433cd4
size 633892
oid sha256:38db9491477a6e0e89cf339aa25b4bd839be3193b9e58433dcd8b8c8b38ce9e2
size 633974

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:875bb700d3411016ff5f08d565247523e56e908a7871f80f8596c939870cbe30
size 2820088
oid sha256:56aed3a621d329704ca101338c075239f85d93f2d0736ef1560cc50795600b7e
size 2821867

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:2358d0379ca37e4e0f51bc8a8b1e1fe991210e40edfa385f04d35384fd9bc726
size 623804
oid sha256:1e6e8b00d0b192b8d730ca3f500142f140e725c60985163377cf559bb7d9b171
size 623208

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:06787cb53e3631f24c903751cfcadc8c28f1e1e128367bc3a939a1eb2c997ce2
size 2367938
oid sha256:dd627231dd9cf8404ea884a0a1bf12df527e5ae037a55f4e89b3ef9dfcf0dc4a
size 2366467

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:0d70d81fd33d710014100658f3cba5f6af703bd39ea5c5c2a66db165f7753a2e
size 306404
oid sha256:ca02e8bcb41f1bf9eacc620e4f7e9df842c9cdfe227f856902768fb9eda3233f
size 306773

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:64e93fb39dc9ecda962b5393bc785bf205b1f3dfffcfc480dd5fb29a770d903f
oid sha256:58e2303b73e9d806ed85ae5f672653696296a4da5ca78d7420c3c625a19c0078
size 1088738

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:c83fa20c9504806d1925589077b0bfa6af9061ffe4e5b16aa2158691efb599d9
size 724225
oid sha256:5bd0e04a64fae423590335de12de7605d18bed609440f905344206ede02b22d2
size 723575

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:702d2731653ab8de5a6dd5f776c680c1089fb344cae4902f95fdde71cb32c334
size 3757694
oid sha256:4dedd9734db98ba96c456f78a98ad30415e653fc10099cf1b0b16860f5225148
size 3758204

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:f4377e7443959ed7c7660cfb5a1d7a97b0e43023c87451f80cbeed804d86cd97
size 607710
oid sha256:b9304e1873fd3527ee94af72bb484f7c7f7b92cfc1a899392bb85ae5f7dec685
size 607951

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:310f45280c9fe6146ce0175668c04969a1c26646b9ee9b175e005ae25d0c6f5c
size 2490818
oid sha256:46a02d7ff12639717788c83e4e4a0f2cf859fad2cb7f3cbdd87289802c928a4a
size 2489685

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:91750353a1e714974a0e39b82688f44417f6b680b605eb7e0cf66f2c14062d27
size 414325
oid sha256:0ecf0f3cb5b4fc7b5f4e96a6472fb3b01be2700c0f3bf4c144848489aa158539
size 414181

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:39264736304c4bd3986e079320330df844f7681e8b8f6be5f858ce7218c24590
size 630561
oid sha256:513380b70b2a5fd30250f71e0fd4521a7c40bc6be35f6b2761093efb80cb194f
size 630539

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:24d0589cec9f792c142d086fd8fbfaa7618e764363266a63d3feb920be08903a
size 391084
oid sha256:1296559334e8c8367179e856a2b6d9d2c3530f7f3b959c001a5a2dfb19db584b
size 390732

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:8d19e80c7d0e3e2229c0897c13106c1cfdcbe0d7936482640017e0bd3f2cc156
size 1700156
oid sha256:be4c9a0770e7287e63d32c174cf0816d3ceaa306a04b499909d3227052d5e9c2
size 1697663

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:5bbd4d8529985a9217be4f883a830471ee0b232be7f51d7fe30e77f2d78d7488
size 359538
oid sha256:431510b758eac4287d48c0769b3268519a10168f234f5f9f9f19dec297f02c00
size 359091

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:73d215987987c8259306265af9b6e6ecde74933727c9f2dd5d54e95667bcc852
size 1340255
oid sha256:a0fa194975263469e1bb75936ca469c5fa2e94a0b3b943cfd0ee3908d9cee839
size 1339467

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:0c5e3157b3e81dc48b63fdca77db3537310b8014a046796df96ca1a6fbf2be8d
size 200833
oid sha256:c359fa963739f59f240ced75a1740c656edf27ca3a2dff7074a5ad30c116b52f
size 200842

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:136003a2a8400fc3555a27f1632665263f60525b2d383e7c4de258317c6b8c5c
size 718973
oid sha256:af9dcaaa0ba739643c2a8b61a479cb2e1fbf1905586169633ededb8b4a3b8285
size 718719

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:336e87c11d1c53e0b6c82133862bbe54607a0e0308787ff96ce3c51aa3089721
size 435180
oid sha256:f7024561fc3ab7bb35fcb27f162eb34773b55656f7803f68087397a69cb97470
size 435548

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:972135ef0a98643b22dc74a61a74206ccd1c1c13d64d450491b9798974d02ea8
size 2215431
oid sha256:8e6fddf09d9d94938d513dfda3f7260a7633df488a6ee83e7afb035aaac5b0a1
size 2217192

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:13ebd3cca09f126c3320fd69e666f1574827d30dbb0886fc7de4e58b52eb46cf
size 371553
oid sha256:792a60dc4e4d45ddb31780d6a66e0069084f546f5be97de092f2b5318b0946ca
size 371486

View File

@@ -1,3 +1,3 @@
version https://git-lfs.github.com/spec/v1
oid sha256:96bf19af3801590af7f973857c69d164a80208fd9542d45db129216a289f6b32
size 1496819
oid sha256:124e8a6997fccf77d32efe73d9e4c30c5d3146d31f7a06b2177716b4effdee67
size 1496431