sanitizers / sanitizers/patchback-github-app

[TODO] Document what privileges a GitHub App needs to fully function

Open
#10 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement good first issue
Dominant language
Python
Stars
14
Forks
10
Avg merge
4m
Merged PRs (30d)
3

Description

Since octomachinery doesn't yet support a structured config for this (https://github.com/sanitizers/octomachinery/issues/40), it should be fine to state this info in README.

FTR, https://github.com/organizations/pyba/settings/apps/patchback/permissions currently has:

Repository permissions

  • Checks: Read & write
  • Contents: Read & write
  • Metadata: Read-only [mandatory]
  • Pull requests: Read & write
  • Single file: Read-only (.github/patchback.yml)

Subscribe to events

  • Pull request

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Update the README with the GitHub App repository permissions and subscribed Pull request event listed in the issue. Check that the documented permissions match the provided configuration, including the mandatory Metadata access and read-only access to .github/patchback.yml.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.