Hi everyone! It's great to see that we are migrating to GitHub, I'm a fan of how GitHub handles the developer experience. I was wondering if while we wait for GitHub swift-issues repo to be unlocked, there's a way to report and document new bugs.
2 Likes
Thank you everyone who provided feedback!
New version of the issues available for feedback: https://github.com/swift-issues-migration/swift-issues-v2/issues
- Added environment filed info from JIRA
- Fixed a typo in the bug report
- Updated username mapping provided after deadline
Any additional feedback please direct message me.
5 Likes
Pandoc supports text conversion from jira to gfm.
Demo: https://pandoc.org/try/?text=&from=jira&to=gfm&standalone=0
I tested headings, text effects, links, lists, tables, code blocks, and emoticons.
(Links with [~username] would need to be further converted.)
2 Likes
Thank you everyone who provided feedback!
New version of the issues available for feedback: https://github.com/swift-issues-migration/swift-issues-v3/issues
- Updated the conversion system to Pandoc (Thanks @benrimmington for the suggestion)
- Fixed the username mapping issue in the comments
Any additional feedback please direct message me.
5 Likes
Thank you everyone who provided additional feedback!
New version of the issues available for feedback: Issues ¡ apple/swift-issues ¡ GitHub
- Parent and Sub-Task links added to the issue
- Jira issue type include as label (Bug, Task, Sub-Task, Improvement, and more)
- Strange line break bug introduced in swift-issues-v3 is now fixed
2 Likes
Please do not modify issues in GitHub - apple/swift-issues: DO NOT MODIFY ISSUES as we are starting the process of transferring issues into apple/swift today.
6 Likes
Should the good first issue label be added to StarterBugs, for the contribute page?
Swift Bugs have migrated to GitHub Issues!
Thank you to everyone who helped provide feedback.
9 Likes
Thanks a ton for doing this! Is there any plan to enable issues on other repos like SwiftPM so the related issues can be moved to that repo?
Yes, they should be enabled now.
It is expected that attached images aren't available? Do they perhaps take some time to process on GitHub's backend with this kind of bulk import?
EDIT: Ah, okay - it's all compressed in the attachment. FWIW macOS/Safari seems to have some issues with the .gz attachment and unpack it in to a blob. You need to manually add another .zip extension to get it to open.
^ - Safari, expanding the .gz in to a blob with no extension.
Another option is to uncheck open "safe" files after downloading in Preferences > General.
Is it ok to already comment on our issues there, or even close them, or should we wait until they have been migrated to the respective repos?
You can start to create and modify GitHub Issues.
4 Likes
Can we safely leave the swift-issues-migration org on GitHub? Why does it still exist if the migration is over BTW?
1 Like
swift-issues-migration org is now deleted.
7 Likes
The last phase is now completed:
- GitHub Issues transferred to corresponding repositories.
- bugs.swift.org URLs will now redirect to GitHub issues.
7 Likes
Awesome, thanks for all the work on that. Now letâs hope that the issues will not just bitrot in another place, but that the move will indeed lead to better visibility and that they get tackled.
Some issue are still in a "Being transferred" status . And some issues are created more than once. Is this a known issue and have some solution for it?
cc @mishal_shah
eg. [SR-15436] Publish SwiftMarkdown as a CocoaPod ¡ Issue #43 ¡ apple/swift-markdown ¡ GitHub
This issue is being transferred. Timeline may not be complete until it finishes.
