Open
Conversation
Per https://developer.atlassian.com/cloud/bitbucket/deprecation-notice-v1-apis/, Bitbucket API version 1.0 is deprecated as of June 30 2018 and will no longer work in April of 2019. Alter the issue fetch methods to use the v2.0 API. Additionally, the "issues" collection is now streamed through the tool in order to support large issue sets with thousands of issues without a large memory footprint. Added a new option --mention-changes that formats status changes as comments; the new Bitbucket API now allows us to have these status changes available. I did notice that the "/changes/" API seems to throw a 500 on at least one issue persistently. The issue in question seems to have a broken assignee on it, so since this is a new API for BB that still has some bugs, it warns for 500 on just the "changes" API and skips.
The TEMPLATE constants are now stored in a local yaml file called templates.yaml, using the same template format (though a real template language with conditionals could be another improvement). The user can now make their own customizing template using the --use-template option.
zzzeek
force-pushed
the
wiki_attachments
branch
2 times, most recently
from
cb8e2ac to
90ff336
Compare
Since github doesn't allow attachments to be uploaded through the API, and requests for this to be added have been ignored for years, work around it by pushing attachment files to the wiki git repo. Add links using relative URLs into the issue so they are both linked and also portable with the repo.
zzzeek
force-pushed
the
wiki_attachments
branch
from
90ff336 to
5dc6687
Compare
jeffwidman
approved these changes
Jan 24, 2019
Owner
|
Looks like this one will also need rebasing. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since github doesn't allow attachments to be uploaded through the API, and requests for this to be added have been ignored for years, work around it by pushing attachment files to the wiki git repo. Add links using relative URLs into the issue so they are both linked and also portable with the repo.
this is all in that line of PRs I have, because they are all building on the previous one, so they keep growing and growing as far as the changesets