Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", + "description": "Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", "inputFields": [ { "name": "input", @@ -87320,7 +87320,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "A git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nAppends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", + "description": "Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", "inputFields": [ { "name": "input", @@ -71487,7 +71487,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "A git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nAppends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", + "description": "Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", "inputFields": [ { "name": "input", @@ -87320,7 +87320,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "A git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nAppends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", + "description": "Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", "inputFields": [ { "name": "input", @@ -66911,7 +66911,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "A git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.
\nSpecify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using nameWithOwner and branch name:
\n{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.
\nSpecify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using nameWithOwner and branch name:
\n{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nAppends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", + "description": "Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", "inputFields": [ { "name": "input", @@ -67743,7 +67743,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "A git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.
\nSpecify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using nameWithOwner and branch name:
\n{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.
\nSpecify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using nameWithOwner and branch name:
\n{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nAppends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", + "description": "Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", "inputFields": [ { "name": "input", @@ -68350,7 +68350,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "A git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.
\nSpecify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using nameWithOwner and branch name:
\n{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepository nameWithOwner and branch name.
\nSpecify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using nameWithOwner and branch name:
\n{\n \"nameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nAppends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", + "description": "Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", "inputFields": [ { "name": "input", @@ -73271,7 +73271,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "A git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nAppends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", + "description": "Appends a commit to the given branch as the authenticated user.
\nThis 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 git commit.
Commits are appended to a branch of type Ref.\nThis must refer to a git branch (i.e. the fully qualified path must\nbegin with refs/heads/, although including this prefix is optional.
Callers may specify the branch to commit to either by its global node\nID or by passing both of repositoryNameWithOwner and refName. For\nmore details see the documentation for CommittableBranch.
fileChanges are specified as a FilesChanges object describing\nFileAdditions and FileDeletions.
Please see the documentation for FileChanges for more information on\nhow to use this argument to describe any set of file changes.
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.
\nA 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.
\nIf you need full control over author and committer information, please\nuse the Git Database REST API instead.
\nCommits made using this mutation are automatically signed by GitHub if\nsupported and will be marked as verified in the user interface.
", "inputFields": [ { "name": "input", @@ -75411,7 +75411,7 @@ "kind": "inputObjects", "id": "committablebranch", "href": "/graphql/reference/input-objects#committablebranch", - "description": "A git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA git ref for a commit to be appended to.
\nThe ref must be a branch, i.e. its fully qualified name must start\nwith refs/heads/ (although the input is not required to be fully\nqualified).
The Ref may be specified by its global node ID or by the\nrepositoryNameWithOwner and branchName.
Specify a branch using a global node ID:
\n{ \"id\": \"MDM6UmVmMTpyZWZzL2hlYWRzL21haW4=\" }\nSpecify a branch using repositoryNameWithOwner and branchName:
{\n \"repositoryNameWithOwner\": \"github/graphql-client\",\n \"branchName\": \"main\"\n}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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}.\nA 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 additions and zero or more\nfile deletions.
Both fields are optional; omitting both will produce a commit with no\nfile changes.
\ndeletions and additions describe changes to files identified\nby their path in the git tree using unix-style path separators, i.e.\n/. The root of a git tree is an empty string, so paths are not\nslash-prefixed.
path values must be unique across all additions and deletions\nprovided. Any duplication will result in a validation error.
File contents must be provided in full for each FileAddition.
The contents of a FileAddition 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.
The encoded contents may be binary.
\nFor 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 (\\n or \\r\\n), and that all files end\nwith a newline.
Each of the the five types of conceptual changes that can be made in a\ngit commit can be described using the FileChanges type as follows:
New file addition: create file hello world\\n at path docs/README.txt:
{\n\"additions\" [\n{\n\"path\": \"docs/README.txt\",\n\"contents\": base64encode(\"hello world\\n\")\n}\n]\n}
\nExisting file modification: change existing docs/README.txt to have new\ncontent new content here\\n:
{\n \"additions\" [\n {\n \"path\": \"docs/README.txt\",\n \"contents\": base64encode(\"new content here\\n\")\n }\n ]\n}\nExisting file deletion: remove existing file docs/README.txt.\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.
{\n \"deletions\" [\n {\n \"path\": \"docs/README.txt\"\n }\n ]\n}\nFile rename with no changes: rename docs/README.txt with\nprevious content hello world\\n to the same content at\nnewdocs/README.txt:
{\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}\nFile rename with changes: rename docs/README.txt with\nprevious content hello world\\n to a file at path\nnewdocs/README.txt with content new contents\\n:
{\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