Integration · GitHub

Capture engineering decisions from GitHub.

Direct answer

Nura processes approved GitHub content to help engineering teams recover decision context recorded in supported pull requests, issues, and discussions. It evaluates the connected evidence to identify the best-supported engineering decision and keeps the answer linked to the original review record.

What Nura captures from GitHub

Engineering decisions live in threads, not just code.

Pull request decisions

Approvals, requested changes, and the reasoning behind a merge.

Issue resolutions

How an issue was ultimately resolved, and by whom.

Discussion threads

Architecture and process decisions made in GitHub Discussions.

Ownership signals

Which team or reviewer is associated with a given area of the codebase.

GitHub search vs company memory

Repository history is not the same as a decision record.

GitHub search

Returns commits, pull requests, issues, and comments that mention a library or policy.

Nura company memory

Helps identify the best-supported engineering decision, who approved it, its scope, and where the review happened.

Engineering decision example

A scoped approval, remembered correctly.

A reviewer approves a new library for backend use only, with a follow-up review flagged for client-side use. Nura remembers the scope of that approval instead of letting it get treated as a blanket yes.

github · connected source

Can we use the new charting library everywhere?

Best-supported answer

Approved for backend services only, pending a follow-up review for client-side use.

DecisionPull request reviewer ? GitHub ? This quarterStatusSupported by connected evidence; verify the original review

GitHub pull requestArchitecture discussion

Different sources. One decision record.

Scope preservation

Engineering decisions keep their review context.

Nura keeps pull request and issue decisions tied to the original review context, so approval scope, requested follow-ups, and ownership do not disappear after the code is merged.

Permissions note

Only approved repositories, only what an admin connects.

Nura processes only GitHub repositories and supported content explicitly authorized for the workspace through the current connector. Repository access is limited by the permissions granted through GitHub and the workspace configuration. Exact supported objects, scopes, historical range, and synchronization behaviour are documented once verified for the current release.

See full security details

Admin-approved repositories

Only explicitly connected repositories are read.

Retrieval-focused access

Nura's current product experience is built for retrieving decision context rather than modifying repositories. Publish a stronger read-only claim only after the installed GitHub App permissions are verified.

FAQs

GitHub integration questions

01Which repositories does Nura read?

Only repositories an admin explicitly connects. Nura does not discover or read repositories on its own.

02Can Nura read private repositories?

Nura can read private repositories an admin has approved, subject to the same access controls already set in GitHub.

03Can admins control repository scope?

Yes. Admins choose which repositories are connected and can adjust that scope at any time.

04Does Nura write code or modify issues?

Nura's current product experience is built for retrieving decision context rather than modifying repositories. A stronger read-only claim should be published only after the installed GitHub App permissions are verified.