Github repository manager

GitHub App powered by AWS Lambda to manage your repositories for you.

Usage

1. Enable this app for the scope you want it to have, per-repository or for your whole account/org

2. Customize it!

Configuration is formed through merging three potential configuration sources if they exist, automatedSecurityFixes and vulnerabilityAlerts are always both enabled by default

1. This repository base-repo-config.yml
2. A specifically named repository in the user/org called .github with a file named repo-config.yml. example
3. A .github/repo-config.yml in the repository

Configuration example

vulnerabilityAlerts: true
automatedSecurityFixes: true
branchProtection:
  - branch: '__DEFALT_BRANCH__'
    # __DEFALT_BRANCH__ is dynamically swapped out for the repository's default branch
    required_status_checks:
      strict: true
      # contexts: ALL
      # if you provide the ALL string for contexts, it will apply all the checks that were run last against the branch
      contexts:
        - build
    required_linear_history: true
    enforce_admins: false
    required_pull_request_reviews: null
    restrictions: null
repo:
  # see octokit docs for all paramshttps://octokit.github.io/rest.js/v18#repos-update
  has_issues: true
  has_projects: false
  has_wiki: false
  is_template: false
  allow_squash_merge: true
  allow_merge_commit: false
  allow_rebase_merge: true
  delete_branch_on_merge: true
files:
  # You can also specify arbitrary files
  '.github/FUNDING.yml': |
    github: [yourusername]
  'SECURITY.md': |
    # Security Policy
    ## Reporting a Vulnerability
    Please contact you@example.com

Installation

You only really need to do this if you don't trust me, want to run on-prem GitHub Enterprise or similar use case.

1. Create a new GitHub App: https://github.com/settings/apps/new

• Use a temporary Webhook URL

1. Download your GitHub App Private Key (i.e. .pem file)
2. Configure this project

• Move .pem into this project and change CERT variable from serverless.yml if required
• Change APP_ID to match your new GitHub App

1. Deploy this project. Check out https://serverless.com/framework/docs/getting-started/ for details.
2. Update your GitHub App's Webhook URL

TODO

• shard the installations, it won't scale well
• support permissions on repo
• manage teams on an org
• manage webhooks

CAVEATS

Using this could do all sorts of things, destroy repos, remove access, basically anything your account can do you're granting to this app and it's author(s) and indirectly the authors of anything in the dependency chain. I'd encourage you to do your own due-diligence before enabling it. The authors/maintainers do not accept any liability of any consequences that occur.