-
Notifications
You must be signed in to change notification settings - Fork 10
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
"Archive" merged repositories #104
Comments
+1 I am fine with that. |
+1 |
In the past it was argued that the old repos will maybe be used for maintenance work (see for example eclipse-pde/eclipse.pde.build#10 (comment)). |
As no one objected I think the proper thing to do is subproject PLs to open helpdesk issues as I believe this is not within our powers. @iloveeclipse Would you please handle Platform? |
This can be achieved self-serve, but the last time I tried that we decided not to do that: eclipse-platform/.eclipsefdn#3 Did something change in the meantime? |
I only saw the pmc approval in this issue and don't know anything more |
I discussed with Alex just now. It's easy to mark a repository as archived and it's easy to undo it in the future if necessary. I'm personally happier to see things marked archived because it's much more clean that the repository is not of interest. The otterdog stuff is really quite easy to manage ourselves: https://github.com/eclipse-platform/.eclipsefdn/blob/main/otterdog/eclipse-platform.jsonnet |
Thanks @merks for keeing in eye out for us. |
Can we undo archive https://github.com/eclipse-platform/eclipse.platform.runtime repos , we are using this repo for our maintenance work. |
Because it appears the changes were not done by modifying the otterdog file, I don't see the changes reflected in that file so I don't know how to undo what was done simply by editing this: https://github.com/eclipse-platform/.eclipsefdn/commits/main/otterdog/eclipse-platform.jsonnet In the future, please let's learn to use this file so we can do things ourselves. Information about this has been shared with everyone: https://www.eclipse.org/lists/cross-project-issues-dev/msg19715.html I know it's unrealistic to expect folks to read what I post. |
Because I cannot reopen https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4071 I've opened this issue: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4072 |
Please make clear on https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/4072 what exactly all needs to be undone. |
Sure, Thanks |
Im new here, so if I have misunderstood this discussion, please forgive me. I am currently in the middle |
No, it's all fine. Sticking to eclipse-platform/eclipse.platform#728 is best. |
We've merged few repos in platform/pde/equinox but the "old" repositories are still there in github and still allow users to create PR's and bugs. Github provides "Archive this repository" action in settings, which makes interactions with archived repo not possible.
We should adk foundation to perform this for the obsoleted repos below.
See https://github.com/iloveeclipse/bytecodeoutline for an example of archived repo.
To be archived:
The text was updated successfully, but these errors were encountered: