gitspork

README

When a fork just ain't good enough

Solutions like git forks or templates are useful, but fall short in certain cases when staying up-to-date with their upstreams. Enter gitspork.

Terminology

• Upstream: a repo that contains some standards, utility, etc. to be distributed to other repos over time. Think of an "upstream" like a git template or a git fork upstream.
• Downstream: a repo that integrates with an upstream repo to reuse its standards and utility. Think of a downstream like a repo that has been forked from another git repo, or generated from a git template.

Features

What gitspork provides for upstream -> downstream integrations

• Upstream-Owned Resources: those that the upstream controls entirely, and will overwrite in downstreams on each integration
• Downstream-Owned Resources: the gitspork integration will make sure these types of files get bootstrapped in the downstream, but then let's the downstream take over full ownership from there
• Co-Owned Resources to be Merged (Generic): certain files can be owned by both the upstream and and downstream, upstream defining blocks surrounded by ::gitspork::begin-upstream-owned-block/::gitspork::end-upstream-owned-block, typically in comments to maintain upstream-owned content alongside downstream-owned content
• Co-Owned Resources to be Merged (Structured Data): json/yaml resources that can be merged in a structured way, with a switch to say whether upstream or downstream values should be preferred/take precedence when doing the merging
• Templated Upstream -> Downstream Rendered Files: Utilizing Go templates, allowing for configuration of JSON data files or user prompts as inputs to fill in the needed data to render the resulting file in downstream, including features:
  • Supporting structured merges after template rendering preferring either upstream or downstream changes in the merge
  • Caching previous prompt input values, allowing the choices to be re-used over numerous integrations
• Drift Detection: downstreams can always easily see if and how they might have drifted from their current upstream version
• Upstream -> Downstream delta resolutions for moves, renames, and deletes. As the upstream evolves, downstreams will follow along with these types of iterations.
• Migrations Support: some ability for the upstream to instruct downstream repos in particular migration-related operations:
  • Exec: arbitrary commands or scripts defined in the upstream to run against the downstream either pre integrate or post integrate

Getting Started

Install

Via Homebrew

brew tap rockholla/gitspork
brew install gitspork

Container Image

Docker/container images are published for every release, and available at: https://hub.docker.com/r/rockholla/gitspork

Manually

Download the appropriate binary from the Github releases, and install on your system's PATH.

Initialize a Repo as a gitspork Upstream

gitspork init

This will initialize a .gitspork.yml file so you can begin configuring how your upstream should share out and integrate w/ downstreams. Run gitspork schema at any time to see the full annotated config reference.

Downstream Integration

From the root of a downstream repo clone:

gitspork integrate \
  --upstream-repo-url [ssh or https upstream repo URL] \
  --upstream-repo-token [if using git https, you can provide your auth token here] \
  --upstream-repo-version [branch, tag, or commit hash from the upstream repo the represents the state you want to integrate with]

Additional Documentation

See ./docs for further information on how gitspork works and usage.

Contributing

See our contributors doc for more info on how to help build out gitspork.