-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
GitBucket API Insufficient for Dependabot Script #3409
Labels
APIv3
GitHub compatible API
Comments
In short, Create a tree API ( |
Yes, at a minimum (I'm inferring that from the error). I don't know what other APIs would be required, if any. I suspect there would be more. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Before submitting an issue to GitBucket I have first:
Issue
Impacted version:
4.40
and earlierDeployment mode: Docker container, with an Nginx reverse proxy for TLS termination (TLS required by Dependabot client)
Issue: GitBucket API support is insufficient to use Dependabot to automatically create PRs for dependency upgrades
Profile
ofroot
, underApplications
, create a new tokenGITHUB_ENTERPRISE_HOSTNAME
set to the DNS name of the TLS terminating reverse proxy, and withGITHUB_ENTERPRISE_ACCESS_TOKEN
set to the value from the previous step, and withPROJECT_PATH
andPACKAGE_MANAGER
setGitBucket
the entryWARN g.c.c.a.ApiGitReferenceControllerBase - git/refs/ endpoint may not be compatible with GitHub API v3. Consider using git/ref/ endpoint instead
dependabot-script
the entrydependabot-script/.bundle/gems/octokit-5.2.0/lib/octokit/response/raise_error.rb:14:in on_complete: POST https://somedomain.local/api/v3/repos/root/testing/git/trees: 404 - Not Found (Octokit::NotFound)
The dependabot script has failed due to a missing API in GitBucket.
The text was updated successfully, but these errors were encountered: