Add build tooling: portable git + git-lfs fork + release CI - #1
Closed
jochenhz wants to merge 2 commits into
Closed
Conversation
build.py builds a portable Git (MinGit on Windows, from-source on macOS) and the Anchorpoint git-lfs fork, drops git-lfs into libexec/git-core/, patches the bundled gitconfig, optionally signs, and packages per-OS archives (git-<os>-<arch>.zip + .sha256) into dist/. Config/env-driven (no interactive prompts) so it runs in CI. The fork is wired as the third_party/git-lfs submodule. .github/workflows/release.yml builds all targets on a v<gitver>-ap.<n> tag and publishes the archives as release assets; signing/notarization and the anchorpoint MinGit flavor are left as documented repo-secret TODOs. Refs AP2-54.
Contributor
Author
|
Integrated into |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Scaffolds the build/publish side of git-dist.
What's here
build.py- builds portable Git (MinGit on Windows via the Git SDK, from source on macOS arm64/x64) and the Anchorpoint git-lfs fork, drops git-lfs intolibexec/git-core/, patches the bundled gitconfig, optionally signs, packagesgit-<os>-<arch>.zip+.sha256intodist/, and with--publish <tag>uploads them to a GitHub release. Config/env-driven (no interactive prompts).third_party/git-lfs- submodule tracking the fork'sap-release-3.7branch (e1e19100, git-lfs 3.7.1 Anchorpoint). Verified locally:go buildreportsgit-lfs/3.7.1 (Anchorpoint; ...), and the tip adds--stdininclude/exclude filters (the selective-fetch feature the app needs)..github/workflows/ci.yml- compile-checks the git-lfs fork across targets +py_compileon build.py. No signing/publishing.config.example.ini.Release model: local
Builds and signing run locally per platform - Windows code-signing uses a short-lived (~3h) token that can't live in CI. Each host runs
build.py --package --publish v<gitver>.anchorpoint.<n>(GfW-style version) to add its archives to the shared release tag (create-or-clobber).TODO before a real release (build host / secrets)
anchorpointMinGit flavor in the Windows Git SDK's build-extra - not in any repo; it comes from the build machine's git-sdk-64. This is the one blocker for a full Windows build.SUBMODULE_TOKEN(PAT, read access to the private fork) for the CI submodule clone.Not tested end-to-end
The git-lfs fork builds and reports Anchorpoint 3.7.1 (verified locally). The full portable-Git build needs the Git SDK + flavor, not run here.
Consumer side (fetch + bundle + portable-git resolver in the app) is a follow-up.