Skip to content

Step 1: Establish baseline vs upstream #4

@Sam-Bolling

Description

@Sam-Bolling

Goal

Establish a precise, reproducible baseline between this fork and upstream so every later review step has a verified change context.

Scope

  • Confirm upstream source and base branch.
  • Identify fork-only commits, files, and high‑churn hotspots.
  • Record a stable reference point for future diffs.

Tasks

  1. Verify upstream
  • Confirm upstream repo: camptocamp/ogc-client (or update if different).
  • Record upstream default branch name and HEAD commit.
  1. Add/refresh upstream remote
  • git remote add upstream https://github.com/camptocamp/ogc-client.git (or verify existing).
  • git fetch upstream --tags.
  1. Establish merge base
  • Determine common ancestor between fork main and upstream main.
  • Record base commit SHA and date.
  1. Fork-only commit list
  • Produce fork‑only commits: git log --oneline upstream/main..main.
  • Categorize commits by area (API, parsers, validators, tests, tooling).
  1. Fork-only files and hotspots
  • List files changed since merge base.
  • Identify top directories by churn (e.g., src/ogc-api/csapi, tests, build configs).
  • Flag new files not present upstream.
  1. Risk flags
  • Note any likely breaking changes (public exports, config, build/test infra).
  • Identify any deleted tests or significant refactors.
  1. Deliverable summary
    Provide a short report with:
  • Upstream reference info
  • Merge base SHA
  • Fork‑only commit list
  • Hotspot files/directories
  • Risk flags

Acceptance Criteria

  • Upstream remote verified and fetch successful.
  • Merge base identified and recorded.
  • Fork‑only commits and files summarized.
  • Hotspots and risks identified with a concise summary.

Output Format (suggested)

  • Upstream: org/repo, branch, HEAD SHA
  • Merge base: SHA + date
  • Fork‑only commits: list (grouped)
  • Hotspots: top dirs/files by churn
  • Risk flags: bullets

Notes

Keep the report short and factual; no remediation yet. That begins in Step 2+.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions