Connect GitHub to ask why the code looks like this and trace a decision from issue to merge

GitHub holds far more than code. The reason a function looks the way it does is usually in a pull request review, an issue nobody closed, or an architecture note in /docs that never made it to the wiki. New engineers reconstruct that from scratch. The GitHub connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.

Ask why the code looks like this

Point a question at a file or a subsystem and get the discussion that produced it — the review comment that changed the approach, the issue that set the constraint — with each one linked so you can read it in full.

Trace a decision from issue to merged pull request

Issue, branch, review, merge: the chain exists, but following it means six tabs. Connected, the chain is one answer, and it survives the person who wrote it leaving.

Search the docs that live beside the code

READMEs, /docs folders, ADRs and wiki pages are searched in the same breath as the discussion, so an onboarding question does not depend on knowing which of those three places the answer was written in.