This repository has been archived by the owner on May 28, 2024. It is now read-only.
Issue Mover #25
Projects
Comments
gundalow
moved this from Before Migration
to "shortly" after migration
in Ansible Community project plan
|
Would it be a reasonable workaround to temporarily move the relevant repo into ansible/ org, move the issue, then move the repo back? |
|
Did we get any response from Github? I've heard that there may exist a bot that helps issue submitters move their own issues, is that a possibility? |
gundalow
moved this from "shortly" after migration
to Backlog (unprioritised)
in Ansible Community project plan
Ansible Community project plan
automation
moved this from Backlog (unprioritised)
to Done
May 23, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We need some nicer to allow movement of issues from gh/ansible/ansible to gh/ansible-collections/REPO.
Built in GitHub functionality only allows Issues to be moved within the same GH Org.
PR mover is solved by #5
I've contacted GitHub to see if they have any ideas
migrated_to_collection_repohttps://github.com/ansible/ansible/labels/migrated_to_collection_repo to moved items.The text was updated successfully, but these errors were encountered: