Skip to content
This repository has been archived by the owner on Feb 8, 2024. It is now read-only.

Move to Qiskit GitHub organization #182

Closed
abdonrd opened this issue Oct 22, 2021 · 0 comments · Fixed by #183
Closed

Move to Qiskit GitHub organization #182

abdonrd opened this issue Oct 22, 2021 · 0 comments · Fixed by #183
Assignees

Comments

@abdonrd
Copy link
Member

abdonrd commented Oct 22, 2021

Issue

We started managing the Qiskit Digital sprints in a GitHub Project from Qiskit/qiskit.org.

And since we cannot link issues/PRs from repositories of other organizations, we have been forced to duplicate many issues, which makes it much more difficult for us to manage.

Solution

After having discussed it in the Qiskit Digital team, we want to create a GitHub Project in the organization, where we can manage everything more easily. And here we have it!

And now we need to move the repository to the Qiskit GitHub organization.
As soon as we move it, we can start managing everything from one place.


We should probably be aware of any implications in automations, like for automatic deployment that might break when changing the org, since they might to try to pull from a GitHub repo URL that isn’t available after the change.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
No open projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant