chore(deps): bump github.com/grokify/gogit from 0.8.0 to 0.10.0

[dependabot]

Bumps github.com/grokify/gogit from 0.8.0 to 0.10.0.

Release notes

Sourced from github.com/grokify/gogit's releases.

v0.10.0

Release Notes: v0.10.0

Full Changelog: grokify/gogit@v0.9.0...v0.10.0

v0.9.0

Release Notes: v0.9.0

Full Changelog: grokify/gogit@v0.8.0...v0.9.0

Changelog

Sourced from github.com/grokify/gogit's changelog.

[v0.10.0] - 2026-09-08

Highlights

• Fleet-wide gitscan pending: sweep unpushed commits across many repositories at once by passing one or more paths (e.g. one per GitHub org you manage), reported per repo with a summary of how many repos were scanned and have work waiting
• New gitscan pushed subcommand and Repo.PushedCommits library API: the most recent commits already pushed on a branch — the counterpart to pending — so you can see recent activity on either side of what has reached the remote
• gitscan pending no longer errors on a branch with no upstream: a repo that was never pushed now reports every commit as pending, resolving the push baseline from the upstream or the matching remote-tracking branch (e.g. origin/main)
• Removed the -d/--dir flag: the scan directory is now a uniform optional positional argument across every subcommand, defaulting to the current directory

Breaking

• The -d/--dir flag is removed from gitscan and gitscan order; pass the directory as a positional argument instead (e.g. gitscan ~/go/src, gitscan order ~/go/src) (542b9c6)
• gitscan pending and gitscan pushed JSON output changed from a single {repo,mode,ref,count,commits} object to an invariant {"repos":[{…}],"summary":{…}} envelope, so consumers never branch on the number of repositories reported (4cb1c1e)

Added

• gitscan pending [path...]: accepts one or more repository or directory paths and reports every discovered repo (concurrently); repos with nothing pending are omitted from the table/markdown views and counted in the summary (4cb1c1e)
• gitscan pending --depth: how many directory levels below each path to search for repositories (default 1) (4cb1c1e)
• gitscan pushed [count] [directory]: list the most recent commits already pushed on the current branch, newest first; count defaults to 10 and is an optional positional (either order relative to the directory) (21882fb)
• Repo.PushedCommits(ctx, limit) and PushedResult: library API returning the most recent pushed commits and the baseline they were read from (21882fb)
• LogOptions.Rev: log commits reachable from an arbitrary revision (e.g. a push baseline) instead of the default HEAD (21882fb)
• gitscan pending shows a live progress bar on stderr while sweeping multiple repositories, keeping stdout clean for piping and JSON (8432515)

Changed

• Repo.PendingCommits now returns a PendingResult carrying the resolved push baseline (upstream, matching remote-tracking branch, or empty when never pushed) so callers can label the report; the CLI adds an unpushed-all mode for branches with no push target (85243b6)
• The commit renderer was generalized from pending-only (PendingReport/Pending) into a shared, list-based CommitReport/Commits API used by both pending and pushed, with an invariant multi-repo output shape (ca377e8)
• The shared recurse flag was scoped per subcommand and root-only flags moved out of the shared file, leaving no shared mutable flag state (542b9c6)

Fixed

• gitscan pending previously errored no upstream configured whenever @{upstream} did not resolve, which also blocked repos that simply had not been pushed yet; it now reports those commits as pending. An unborn or detached HEAD yields no pending commits rather than an error (85243b6)
• Build-from-source instructions in the README pointed at the wrong directory and build path (cd gitscan / go build .); corrected to cd gogit / go build ./cmd/gitscan (54a31fa)

Documentation

• README and docs/index.md: documented fleet pending, the pushed subcommand, the positional scan directory, and the previously-undocumented since --unpushed flag (54a31fa)
• README: recorded fleet-sweep cold/warm cache performance (~22s cold vs ~5.5s warm across ~640 repos) and a planned --modified-since prefilter to skip unchanged repositories (34d6428)

Tests

• Coverage for PushedCommits (upstream, limit and newest-first ordering, no-upstream), fleet pending (multi-repo grouping, summary, and the single-repo --since-commit guard), and the list-based renderer (fleet hiding of clean repos, JSON envelope shape, and per-repo error reporting) (4cb1c1e)

[v0.9.0] - 2026-09-07

Highlights

• New gitscan pending subcommand and Repo.PendingCommits/Repo.HasUpstream library API report commits that exist locally but haven't been pushed, or that come after an explicit commit hash — as an aligned terminal table, copy-pasteable markdown, or JSON for agents
• gitscan pending timestamps are now RFC 3339 with an explicit UTC offset and a weekday column, with a new --tz flag to normalize every timestamp to local or utc instead of each commit's own recorded offset
• Consolidated two independent, disagreeing AI co-author detectors onto one canonical registry, fixing a bug where a bare "Claude Code" co-author was misread as model "Code"

... (truncated)

Commits

• 5208d4a docs: point the Releases link at v0.10.0
• ee50a71 chore(release): v0.10.0
• 54a31fa docs: document fleet pending, the pushed command, and positional dir
• 34d6428 docs: note cold/warm cache behavior and a skip-unchanged-repos idea
• 8432515 feat(cmd): frame fleet pending with a progress bar on stderr
• 4cb1c1e feat(cmd): sweep pending commits across many repositories (fleet mode)
• 21882fb feat(cmd): add pushed command to list recently pushed commits
• ca377e8 refactor(render): generalize the pending renderer into a shared commit renderer
• 85243b6 fix(pending): list all commits when the branch has no upstream
• 542b9c6 refactor(cmd)!: unify directory args and scope flags per subcommand
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 47bb2066-d661-451e-9d04-83ffc4967e23

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}