-
Notifications
You must be signed in to change notification settings - Fork 539
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
Bitbucket docs #207
Comments
Add -e CONFIG.GIT_PROVIDER=bitbucket |
Is this for bitbucket SERVER or cloud? |
/similar_issue |
The docs could be clearer on if this applies to bitbucket cloud only or can be used for bitbucket server / datacenter as well. |
You are welcome to open a PR to improve the docs. |
I'm sorry, how would we know what to put in the docs? You want the
community to reverse engineer your code and write the docs or what are you
saying?
…On Thu, Mar 14, 2024, 12:22 Tal ***@***.***> wrote:
The docs could be clearer on if this applies to bitbucket cloud only or
can be used for bitbucket server / datacenter as well. On-premise usage in
general is not very well explained in the documentation.
You are welcome to open a PR to improve the docs.
There are many git providers and sub-frameworks, and we rely on the
community to cover so many options.
—
Reply to this email directly, view it on GitHub
<#207 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AE5FPXBLDZ6SCN3O37DN243YYHFDFAVCNFSM6AAAAAA3PK5LFKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOJXHA2DAMBUG4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
I was also confused for a bit, because the documentation says it wants a "bearer token" but that name was not what I expected. After a bit I realized a repository access token will do. If you use bitbucket cloud:
You might get an error |
How to setup bitbucket with docker. when running the command line, it says GITHUB.USER_TOKEN is required
The text was updated successfully, but these errors were encountered: