BitBucket supports embedded images in issue comments, which seem to be hosted on bitbucket. When an issue is migrated to GitHub, the URL is unchanged. If the BitBucket repo is public, I assume the images will appear to work in GitHub, at least until the BitBucket repo is deleted. However, if the BitBucket repo is private, the images do not show up in the GitHub issue.
The obvious solution would be to download the image from BitBucket, then somehow upload it to githubusercontent.com and link to it in the same way as images are handled in GitHub issues. However, according to this post, this might not yet be possible through the GitHub API.
Maybe another option would be create a new Gist, then clone the Gist as a repository and add the file to it, then push it back. The file should then be accessible via its raw URL, and a markdown link could be created in the issue to replace the BitBucket URL.
BitBucket supports embedded images in issue comments, which seem to be hosted on bitbucket. When an issue is migrated to GitHub, the URL is unchanged. If the BitBucket repo is public, I assume the images will appear to work in GitHub, at least until the BitBucket repo is deleted. However, if the BitBucket repo is private, the images do not show up in the GitHub issue.
The obvious solution would be to download the image from BitBucket, then somehow upload it to githubusercontent.com and link to it in the same way as images are handled in GitHub issues. However, according to this post, this might not yet be possible through the GitHub API.
Maybe another option would be create a new Gist, then clone the Gist as a repository and add the file to it, then push it back. The file should then be accessible via its raw URL, and a markdown link could be created in the issue to replace the BitBucket URL.