Follow ups from repository audit

TODOs

Apps

• background-check (Type: App (by @itaditya)): Ask @itaditya, otherwise archive.
• dco (Type: App): Ask if someone is interested in owning it
• reminders (Type: App (by @jbjonesjr and @bkeepers)): Archive it and add note to build this with actions instead. Maybe in future we can refactor it to use probot/action
• stale (Type: App): Obsolete because people should use Actions instead.
  
  Make a plan, Actions will be available to everyone after Universe.
  
  Concern: will it eat up free Action minutes available
  
  Shown in GitHub MArketplace as owned by GitHub
• unfurl (Type: App): should be obsolete because of content-reference (but might be a valid alternative due to lack of limit of URLs)
  
  Did not cause maintenance overhead
• view-rendered (Type: App): not obsolete

Extensions

• attachments (Type: Extension): Add a note to the README, link to the content-attachement API documentation. Is still useful as it is not limited to a single domain
• metadata (Type: Extension): Keep it. There is no better replacement.

DONE

• talks (Type: Meta): Does not cause support burden.
• autolabeler (Type: App): Ask @mithro if we should move it to their account
• chaos-monkey (Type: App): Asked Wil to move to his account
• create-probot-app (Type: Core): Needs some love ❤
• enforce-template-app (Type: App): Ask @Rahmeen14 and @Akshitaag if they want repo moved. Otherwise archive.
• first-timers-only-app (Type: App): Ask @Rahmeen14 and @Akshitaag if they want repo moved. Otherwise archive.
• hello-world (Type: App): Keep it. Already deployed to Glitch
• ideas (Type: Core): Keep it. Gregor will take ownership
• invite (Type: App): Keep it. Nice showcase for OAuth coming in v10. It’s pretty cool, honestly 🙂
• linter (Type: App): Archive it. Add note to use Actions.
• scheduler (Type: Extension): @tcbyrd: The Stale app depends on this, but yeah in general I think going forward any new apps should just use the scheduled action, which can post to another API if needed.
• serverless-gcf (Type: Core): Should become obsolete or easier with Probot v10
• serverless-lambda (Type: Core): Should become obsolete or easier with Probot v10
• smee-client (Type: Core)
• smee.io (Type: Core)
• metrics (Type: App): Ask hiimbex. Already archived since 2+ years, we recommend deleting.
• mistaken-pull-closer (Type: App): Archived
• no-response (Type: App): Archived
• now-github-starter (Type: Fork): Deleted
• probot.github.io (Type: Core)
• probot (Type: Core)
• stale-action (Type: Action)
• weekly-digest (Type: App): created during GSoC, as Abijeet to move to own account
• twitter (Type: Meta): Used to collaborate on tweets from @ProbotTheRobot
• .github (Type: Core): Keep it
• autoresponder (Type: App): Keep as demo app.
• commands (Type: Extension): Same as Meta Data. Not replacable by GitHub APIs yet.
• duplicate-issues (Type: App): Archived
• eslint-config-probot (Type: App): Archived.
• friction (Type: Meta): Archived
• github-app (Type: Core): Archived
• probot-config (Type: Extension): Archived. Already has a note in README.
• probot-now-starter (Type: Core): Archived. Revisit after Probot v10
• probot-ui (Type: Extension-ish): Archived
• semantic-pull-requests (Type: App): Should move to @Zeke S’s account. WIP: https://github.com/conventional-commits/conventionalcommits.org/issues/199
• settings (Type: App): Archive it. Add note that the app will continue to run but no core Probot maintainer can maintain the app right now. @travi offered to help maintain the app. @gr2m will help with reviews and deployments.
• template-typescript (Type: Core): Archived. Templates live in create-probot-app
• template (Type: Core): Archived. Templates live in create-probot-app
• test (Type: Meta): Archived.

Backlog

• auth-routes (Type: Extension for OAuth login): Will probably become obsolete with next Probot version

[AaronDewes]

• attachments (Type: Extension): Can be archived because of new content-attachement API. Add a note to the README, link to the content-attachement API documentation

I think this is still useful, because content-attachement is limited to a few specific URLs.

[zeke]

✅ I moved https://github.com/zeke/semantic-pull-requests and moved it to the Done list (and sorted the Done list alphabetically)

<div> GitHub</div><div>zeke/semantic-pull-requests</div><div>Ensure your pull requests follow the Conventional Commits spec - zeke/semantic-pull-requests</div>