Amoreg × GitHub
Amoreg reads repositories, issues and pull requests for engineering evidence and context.
- Kind
- Plugin
- Connected by
- Each person, for themselves
- How
- Each person signs in with GitHub
- Access
- Reads freely; acts only when you ask
What Amoreg does with GitHub.
- 01
Engineering evidence
Pull requests and reviews as evidence for change management controls.
- 02
Issues as context
See the engineering work behind a finding.
- 03
Yours alone
A personal plugin with exactly your access.
Ask in plain words. Tag @GitHub.
Mention it in any chat and Eve reads what the request needs, cites what it used, and asks before anything that sends.
How it connects. Each person, for themselves.
- 1Open Plugins and connect GitHub.
- 2Each person signs in with GitHub.
- 3Tag @GitHub in any chat. It follows you into every organization you belong to.
- GitHubReads freely; acts only when you askConnected
- Signed in asYou, with your own accessPersonal
- Follows youInto every organization you belong toYours
Who connects GitHub. Firms like these.
It comes up most around regulatory change management, thematic review and operational resilience.
Questions.
Who connects GitHub?
Each person connects their own GitHub. It belongs to them and follows them into every organization they belong to; nobody else can use it.
What can Amoreg see in GitHub?
Reads freely; acts only when you ask. Each person signs in with GitHub, so Amoreg reaches no more than that connection allows.
Does Amoreg change anything in GitHub on its own?
No. Eve acts only when someone asks, and anything that sends email waits for that person’s approval of the exact message.
