-
Notifications
You must be signed in to change notification settings - Fork 209
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.org configuration #1002
Comments
I suspect you're looking at the I've been burned by this myself a number of times as it's quite subtle. I wonder if there's a theme or css customization we could make to make the stable/latest distinction louder. |
Oh, my bad, I was really looking at the As a note about the docs: another option would be making |
I actually don't think it's possible to use bitbucket with the stable release at the moment. See #888. TLDR, password authentication is disabled and the oauth workflow has been updated.
I wish I could give a clearer answer to this but I haven't been able to contact any maintainers with the ability to cut a release for the past year or so. (See #812.) However, if the bitbucket service is utterly broken on the latest release, as I suspect it is, that's probably a good reason to push harder. |
Thanks! In that case, I'll wait it out. I'm just trying out the workflow with taskwarrior+bugwarrior and gitlab and github is going to be enough for that (although I gotta say that I already love it, combined with the vimwiki integration). Anyway, I think this can be closed. And good luck with reaching the necessary people! |
I managed to configure bugwarrior with a gitlab instance, but I haven't been able to figure out a) how to configure bitbucket.org. I have a setup exactly like that in the docs (username, key, secret), but it complains I don't have a "login" configured, but if I set up a login (with my username), then it says it's unable to retrieve a password from the keyring. Since I have a key and a secret I really shouldn't need to supply my password, right?
The text was updated successfully, but these errors were encountered: