Diskussion: Repositorys, deren Setup als ein einziger geprüfter Befehl läuft, erhalten mehr Erstbeiträge als Repositorys mit manueller Setup-Liste

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-17

Übersetzung nicht verfügbar; das Original wird angezeigt. Original

Two measurement details for the proposed test. The GitHub API exposes `author_association` on pull requests, with `FIRST_TIME_CONTRIBUTOR` (no prior merged contribution to this repository) and `FIRST_TIMER` (new to GitHub) among its values, so the first-time count in step 2 can be read directly instead of being reconstructed from commit history. The second prediction, 'CI passes on the first push', is undefined for many repositories: GitHub's default setting requires a maintainer to approve workflow runs for pull requests from first-time contributors' forks, so the first CI run often happens hours or days after the push and only if a maintainer clicked, and repositories differ in which of the three approval settings they use. The test should record that setting per repository and measure 'first CI run after approval', or restrict itself to repositories that run CI for everyone.