-
Notifications
You must be signed in to change notification settings - Fork 245
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error `merge_base': object not found - no match for id #404
Comments
I am not git expert |
Ran into and fixed this, myself. Albeit the fix was removing depth which isn't ideal. I believe this happens because Rugged, the dependency pronto uses, can't crawl your git history to get your merge base between your branch and the compared branch (I'm assuming main/master). This happens if your supplied I don't know if there's a good way around it. If you're using depth because of a large git repo, you can consider setting a high depth or a long |
We just ran into this, and I'm playing around with something like:
That's probably not correct yet tho. |
I had a similar problem but it was because the initial checkout defaults to
.. where 100 is arbitrary but hopefully big enough to cover all commits on the feature branch since it was forked from master. |
After years of it working fine, I've suddenly started seeing the same error when running on CircleCI ("object not found - cannot read header for (7c12bff1f6ffc4e442e24949edcf31cdbe438fb0)"), but unlike suggestions above, CircleCI doesn;t use a shallow clone. When I SSH onto the CI box and run |
Like @KieranP after years of it working fine on CircleCi, I've seeing this error repo = Rugged::Repository.new('path/to/my/repository')
repo.exists?("d7655e8ce194095299e5d85b4650d2a66f004b26")
# => false The same CircleCI configuration on another rails app, same version of Ruby and of Rails, does not produce this issue 🤔 |
I think I have a clue, comparing the CI on this 2 similar app (same versions of Ruby/Rails/Pronto/Pronto-Rubocop and same |
@quarkgluant Hmm, so CircleCI may have changed how their 'checkout' helper step operates. As a workaround, I added this to my config, which seems to fix it:
|
Got a similar error :
My fix was adding
|
We've encountered an error when using code for github actions integration:
The solution was to remove
--depth=10
fromgit fetch --no-tags --prune --depth=10 origin +refs/heads/*:refs/remotes/origin/*
. I'm leaving it here, may be useful for someone, but maybe there is something better we can do to get rid of this error?The text was updated successfully, but these errors were encountered: