-
Notifications
You must be signed in to change notification settings - Fork 50
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: fallow-rs/fallow
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: v2.57.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: fallow-rs/fallow
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: v2.58.0
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 5 commits
- 26 files changed
- 1 contributor
Commits on Apr 30, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 4e24698 - Browse repository at this point
Copy the full SHA 4e24698View commit details -
Configuration menu - View commit details
-
Copy full SHA for 24c4a2a - Browse repository at this point
Copy the full SHA 24c4a2aView commit details -
feat(coverage): add
upload-source-mapsCI subcommandScans a build output directory for `.map` files and POSTs each to `/v1/coverage/{repo}/source-maps` so cloud-mode runtime coverage can resolve bundled paths back to original source files. Defaults match common CI shape: `--dir dist`, `--include **/*.map`, exclude `**/node_modules/**`, repo from package.json `repository.url` or `git remote get-url origin` (trimmed to bare repo name), git SHA from `$GITHUB_SHA` / `$CI_COMMIT_SHA` / `$COMMIT_SHA` / `git rev-parse HEAD`. API key is read only from `$FALLOW_API_KEY` to keep the secret out of argv. Per-map retry on network/`429`/`5xx`, warn at 10 MiB, reject at 100 MiB. Repo segment is percent-encoded so `owner/repo` becomes `owner%2Frepo` in the URL. Exit codes: 0 ok · 1 partial-failure · 2 validation.Configuration menu - View commit details
-
Copy full SHA for f984856 - Browse repository at this point
Copy the full SHA f984856View commit details
Commits on May 1, 2026
-
feat(hooks): add
fallow hooks install --target {git,agent}namespaceIntroduces a unified `fallow hooks install|uninstall --target <git|agent>` command surface so the Git pre-commit hook scaffolder and the Claude / Codex agent gate share one entry point. `fallow init --hooks` and `fallow setup-hooks` remain as compatibility aliases that delegate to the new engine. The generated Git pre-commit hook now resolves the base ref at commit time: UPSTREAM="$(git rev-parse --abbrev-ref --symbolic-full-name '@{upstream}' ...)" if [ -n "$UPSTREAM" ]; then BASE="$(git merge-base "$UPSTREAM" HEAD 2>/dev/null || echo "$UPSTREAM")" else BASE="<fallback>" fi fallow audit --base "$BASE" --quiet Diffing against the merge-base with the upstream is the topology-agnostic answer for repos with multiple long-lived integration branches (next-release / hotfix / LTS): a feature branch forked off a non-default integration branch compares against the right fork point, not against its own remote tracking branch. `--branch` is repurposed as the fallback used only when no upstream is set. Includes managed-hook detection via a `# Generated by fallow hooks install --target git.` marker so `hooks uninstall` preserves user-authored pre-commit scripts unless `--force` is passed, plus `--dry-run` for both install and uninstall. Closes #242Configuration menu - View commit details
-
Copy full SHA for e66b0ff - Browse repository at this point
Copy the full SHA e66b0ffView commit details -
Configuration menu - View commit details
-
Copy full SHA for bf49e80 - Browse repository at this point
Copy the full SHA bf49e80View commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v2.57.0...v2.58.0