Closed merks closed 10 months ago
@akurtakov
If you look at Mylyn
https://github.com/orgs/eclipse-mylyn/repositories
you can see that some (most) repositories are marked as archived:
I think that because they are marked that way like via this archived: true
property:
Probably it's good for the platform to do this as well so that one can see at a glance what's not relevant anymore.
@netomi Please wait for @akurtakov to agree to this change.
indeed, setting the property archive to true has the effect as you point out.
Repositories have not been archieved as that would make it impossible to backport fixes for old release branches and some companies still do that. Please correct me if I'm wrong and one can still push to archived repository. @sravanlakkimsetti What is IBM stand on this one?
Archived repositories can indeed not be modified anymore so no commits can be pushed to them anymore. So if you plan to push some commits to them in the future you should not mark them as archived, though the archive flag can be removed at any time.
Usually a repo is archived to indicate that development has been deprecated or moved on to another repo, e.g. when moving a project to another location like Gitlab or its own GitHub organization.
I think that does make it read only because I see this in the banner of such a repo:
So if that's bad, then we dont' want this change...
ftr: the content of these repos has already been adjusted to that:
Master branch is empty but all the R_* branches are still there is people want to backport.
Closer inspection of the repo https://github.com/eclipse-platform/eclipse.platform.text shows that commits / releases still seem to happen on a regular basis:
Maybe that should be reflected in the README.md of the master branch to avoid confusion, I would suggest to close this PR then.
Mark repositories that have been merged into other repositories as archived.