Y
Yaniv Gutman
After moving from the old GitHub App to the Ocean-powered GitHub integration (which is supposed to keep full parity), some data is missing:
Branch fields that used to be mapped, such as:
last_contributor (e.g., .branch.commit.commit.author.email)
last_push / last commit date (e.g., .branch.commit.commit.committer.date)[Map repos]
Other repository-related data (e.g., data used for tags).
This breaks existing mappings and examples that rely on these fields, even though the new integration is announced as keeping parity with the old one.
Impact
Existing blueprints, mappings, scorecards, and workflows that depend on last contributor / last push no longer work.
Production readiness and activity signals become inaccurate.
Migration to the Ocean integration is not a drop‑in replacement and becomes risky.
Request
Restore branch-level fields in Ocean
Make branch data available so we can map:
last_contributor (author of last commit on default branch)
last_push / last commit date
Expose repository-level data at least at the same level as the old GitHub App (including data needed for tags and similar use cases).
Add an Ocean-based example equivalent to “Map repositories and last contributor” in the docs.
Acceptance Criteria
In the Ocean GitHub integration:
last_contributor and last commit date for the default branch can be mapped and mirrored to the repository entity.
Repository metadata (including tag-related data) is available with parity to the old GitHub App.
Documentation includes:
An Ocean-based “repositories + last contributor” example.
Created by Oladipupo Ibeun
·