Repository Linter@SAP
summary
An internal GitHub App runs scheduled runs every 24 hours and flags missing community files (README, CONTRIBUTING, SUPPORT, GOVERNANCE, CODEOWNERS), repo visibility and branch protection, plus SAP‑specific rules; results post to a dashboard as a pinned GitHub issue. Missing files get automated PRs from template repos so maintainers can adopt standardized content. A basic lint run scans repos without the app installed. The tool is installed in ~300 repositories, most findings remain unaddressed; plans include more rules, content checks and reminder notifications.
AI-written summary · about
chapters (7)
- 0:00Introduction to Repository Linter
- 1:15Discovering Inner Source projects
- 2:23Standardizing project setup
- 4:11What the linter checks
- 6:28Technical setup of the linter
- 9:00Live demo of the linter
- 13:43Current state and future plans
related talks
31mHow GitHub uses linters
25mDriving the InnerSource Program at SAP
08mAutomated Checks Before Publishing Open Source, a Few Years La...
27mRules_lint: Formatting and Linting All Languages
37mEstablishing a Baseline: Repo Metrics, Ma...
37mHow to Serve Open Source Maintainers Without Annoying Them?
24mKeeping Code Style Sanity in a 13-year-old Codebase
22mGetting Started with Open Source Project Insights