Working with outside collaborators can add more work for a repo owner, from confirming access to changing permissions.
To keep up with manual housekeeping for one shared org, we decided to use Evergreen: a GitHub App built with native GitHub features.
The workflow 👇
github.blog/engineering/pl…
To keep up with manual housekeeping for one shared org, we decided to use Evergreen: a GitHub App built with native GitHub features.
The workflow 👇
github.blog/engineering/pl…
Oct 24, 2026 · 4:55 PM UTC
22
14
140
29,222
@github every org has one contractor from 2019 who still has admin
0
0
0
63
@github Automating collaborator housekeeping with native GitHub features beats handing org-wide permissions to yet another third-party bot.
0
0
1
135
@github permissions housekeeping is the kind of thing i'd script before lunch and forget about
0
0
1
159
@github making collaborator access upkeep automatic is a nice quality of life upgrade
0
0
1
74
@github Small businesses need this hygiene even more than big orgs. Freelancers come and go, and their access to repos, payment dashboards and shared drives often outlives the contract. A monthly 10-minute access review closes most of that risk.
0
0
0
54
@github Access cleanup is the chore everyone postpones until a stale collaborator becomes an incident. I would want the agent to propose removals and leave the revoke button to a human.
0
0
0
61
@github 外部協力者の権限は、招待時だけでなく終了時の見直しも大事ですね。自動化するなら、付与理由・期限・変更前後の差分を残したいところです。まずは権限を変えず一覧を出す運用から始めると、削除対象の判断を確かめやすそうです。
0
0
0
22









