Closed sarroutbi closed 2 weeks ago
Why fork and archive, instead of a clean transfer that would retain all the history ?
Why fork and archive, instead of a clean transfer that would retain all the history ?
That is a good question. They decided to fork in OpenShift organization, but I can not clarify why, sorry for that. Once forked, it seems all the history (talking from Git perspective) is kept, right?
I was referring to issues and PRs, but if that is a done deal I am ok archiving this one.
I was referring to issues and PRs, but if that is a done deal I am ok archiving this one.
Regarding PRs, the only two opened have to do with CI and don't apply, as the operator will be migrated to Konflux. Regarding issues, I will transfer the ones that apply to OpenShift/Konflux new environment. The other ones will be closed.
Thanks @simo5 for your quick responses
Hey @sarroutbi thanks for the update, I am following along on the new repo. Take care, Paul
Hello. tang-operator repository in latchset organization has been forked to OpenShift organization:
https://github.com/openshift/nbde-tang-server
I would like to check if anybody subscribed to this repository is against https://github.com/latchset/tang-operator archival