Skip to content

https://github.com/github/docs/issues/27855 #43217

@pmjthusin-gif

Description

@pmjthusin-gif

I think this is still not fully solved.

single_file / single_file_paths are documented in URL-parameter docs, but there is still no clear permission/capability mapping in the main GitHub App permissions docs.

In practice, it’s unclear which REST/GraphQL write APIs are expected to work with Single file scope (for example, createCommitOnBranch can fail with Resource not accessible by integration).

Could docs add a small compatibility table for Single file scope:

  • supported REST endpoints
  • supported/unsupported GraphQL mutations
  • recommended API path for updating exactly one file

That would make least-privilege app setup much easier.

Originally posted by @DCjanus in #27855

Metadata

Metadata

Assignees

No one assigned

    Labels

    invalidThis issue/PR is invalidtriageDo not begin working on this issue until triaged by the team

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions