-
Notifications
You must be signed in to change notification settings - Fork 4
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
Migrate from waffle #397
Comments
I am trying out GitHub projects for the skohub project. Until now it hasn't been much fun, e.g. I can not link additional repos to the project. The description from https://help.github.com/en/articles/linking-a-repository-to-a-project-board does not work. (I do not get the "Settings" option.) |
The problem was that I did create the project under in repo and not directly under the hbz organization. Now it worked, see https://github.com/orgs/hbz/projects/1. |
I used the automatic migration offered by waffle to migrate to GitHub projects. The result is not that good as waffle obviously kept some labels after an issue was closed. So there are lots of closed tickets popping up in the different columns: https://github.com/orgs/hbz/projects/2?fullscreen=true I should have cleaned up the labels before migration. As migration is only possible once for each Waffle project, I can do it again and will clean up the board manually. Good news is: You can now link up to 25 repositories to a project. But currently I don't even know what it means as you can obviously add issues from a not-linked repo to a project board as @fsteeg did with hbz/lobid-resources#986 and the SkoHub project. |
Re. the purpose of linking a repository it reads at https://help.github.com/en/articles/linking-a-repository-to-a-project-board:
So it is easier to link an issue from the board. As with our workflow we probably are adding issues from the issue template when creating it, there is now difference between linked and unlinked repos... |
It looks quite good now: https://github.com/orgs/hbz/projects/2?fullscreen=true I suggest to delete the waffle project after standup to complete the migration. |
I now also removed the waffle project. From now on, we will work with https://github.com/orgs/hbz/projects/2 as our main Kanban. Closing. |
As @literarymachine made me aware, waffle.io will be shutting down by 2019-05-16. See the blog post at https://blog.waffle.io/farewell-from-waffle-%EF%B8%8F-794da4a72851.
We will have to think about migrating to another online Kanban board, probably GitHub projects, see the migration help and FAQ.
As the FAQs say, GitHub projects unfortunately currently only supports up to five repos in one project.
The text was updated successfully, but these errors were encountered: