-
Notifications
You must be signed in to change notification settings - Fork 70
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
Graduate to conda organization #352
Comments
I'm on board with this graduation. (Though I suggest |
The name here mirrors that of other setup actions in the GHA ecosystem, (e.g., |
+1 for the name of the action indicating what it's setting up, i.e. continuing to mirror the ~replacement |
I would also be in favor of naming it The only thing to consider here is that we would lose all issues for the new repository since "graduating" here would probably mean creating a new repository instead of transferring. The way I read the GitHub documentation, transferring and renaming would break existing workflows that point to From the Transferring a repository documentation.
And further from the Renaming a repository documentation.
|
@marcoesters FWIW I'm aware of this limitation on GitHub's side, this ticket is about whether we want to do this step in the first place, per the conda governance policy about incorporating a project into the main conda community organization, less about how it's implemented. |
My original intention for the name was for it to be See: https://github.com/marketplace/actions/setup-conda So the repo can be whatever we decide. So I am not even sure if the name change is possible. Since this would be a more "official" conda action, we could ask And 👍🏼 on graduating :) |
@conda-incubator/setup-miniconda
I'd like to propose graduating setup-miniconda to the main conda organization and merging the @conda-incubator/setup-miniconda team with the fledgling
installer
team, that I started in conda-incubator/installer#1, to bolster our ability to maintain it. I believe that would put a little energy into this effort and distribute the maintenance burden a bunch.Also, since
setup-miniconda
supports multiple and custom installers (not just miniconda, despite its name), I would suggest renaming the repo toconda/setup-action
as part of this process. Especially since GitHub doesn't ship a miniconda installation by default in the newest worker images anymore, it's worth making sure this is well-maintained.The difference to the also existing @conda-incubator/constructor is that the installer and setup-miniconda teams are both downstream users of the constructor technology.
The text was updated successfully, but these errors were encountered: