-
Notifications
You must be signed in to change notification settings - Fork 1
Should this repo be archived? #12
Comments
Are the CF-2 issuse now discussed under cf-convention/cf-conventions? Some of the issues here are still open and still relevant to the CF convention evolution - like the use of the new user types. Should these be moved or re-opened as cf-conventions issues? |
I think that would make sense. The one I'm responsible for is done. Maybe we just comment on each one @thepersonwhostartedit and tell them to move it to cf-conventions if it's still relevant? |
How can the issue be moved to cf-conventions? Is there an option to do this or shall I just open it again under cf-conventions with a link back here for the previous discussion? |
How can the issue be moved to cf-conventions? Is there an option to do this
Seems like it is possible: https://help.github.com/en/articles/transferring-an-issue-to-another-repository.
or shall I just open it again under cf-conventions with a link back here for the previous discussion?
That's how I'd do it because it is guaranteed to work regardless of the user's permissions in the source and target repositories.
|
I see the "Transfer Issue" button. How about I transfer the ones that seem to still be relevant and comment at the person who started the ones that aren't obvious? |
Sounds like a good idea. |
If this notification makes it to anyone that objects -- please object. Otherwise, I will archive next time I decide to clean up github stuff.
The text was updated successfully, but these errors were encountered: