jfrog / jfrog/frogbot

[Bug] scan-repository fails with "core.repositoryformatversion does not support extension: worktreeconfig" in v2.33.0

Open
#1,333 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
372
Forks
107
Avg merge
2d 20h
Merged PRs (30d)
5

Description

Regression: works in v2.32.3, fails in v2.33.0 (introduced by the dependency bump in PR #1322).

Root cause: git sparse-checkout writes extensions.worktreeConfig = true into .git/config. The version of go-git pulled in by v2.33.0 validates git repo format extensions strictly and doesn't recognise worktreeConfig, failing immediately at repo open.

Error:

  [Info] Frogbot version: 2.33.0
  [Info] Running Frogbot "scan-repository" command
  [Info] Getting resources (git repository: ...) active watches...
  [Error] core.repositoryformatversion does not support extension: worktreeconfig

Repro: run actions/checkout with sparse-checkout: configured before the Frogbot step, then run frogbot scan-repository.

Workaround: run git sparse-checkout disable before Frogbot runs.

Fix suggestion: upgrade to a go-git version that supports worktreeConfig (standard since git 2.20).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by tracing the dependency bump in PR #1322 and the repository-open path used by the scan-repository command. Reproduce the failure with actions/checkout sparse-checkout enabled, then verify that repositories containing extensions.worktreeConfig open successfully without the reported error.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, go
Domain
devops, security
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
62/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.