-
Notifications
You must be signed in to change notification settings - Fork 209
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
Move Chaosthebot/Chaos (v1) to Chaos-Legacy #561
Comments
We also need a general discussion repository to convert Project cards to issue to discuss them. This repository will contain only a Readme, a Contributing (and? the Code of Conduct). Examples : isaacs/github, waffleio/waffle.io, |
I can create a repo for general information and discussion, which could eventually have commands for project management and adding cards. |
@amoffat @Swizz I've created a Chaosthebot/Chaos-General repo for general discussion and information. I think we could continue #559, #561, #562, #563, #564 and #565 (possibly #553 as well) over there. (I believe there is a tool to automatically copy issues over from one repo to another, but I'll need to look into it later.) |
Only opening new fresh ones which reference old ones, will not be sufficient ? We also need to convert your project card into issues. |
I propose that we rename the legacy repo to something like Chaosthebot/Chaos-Legacy, which would help clear room for v2 (as I'm assuming all of v2 will be in new repos).
The text was updated successfully, but these errors were encountered: