Open kenodegard opened 3 weeks ago
Personally I'd rather stick to one code infrastructure for this, instead of two, even if it feels over the top to just sync the CoC document, it's still a smaller effort to use the same system and rely on fewer 3rd party dependencies.
Checklist
What is the idea?
Should we force all conda org repositories to use the new
update.yml
workflow? And then delete the oldsync.yml
workflow from here?We have successfully migrated most repositories over to the new
update.yml
workflow. Those that remain are those that only sync theCODE_OF_CONDUCT.md
and adding theupdate.yml
workflow to those repositories is somewhat over the top.Why is this needed?
To delete old/unused code.
What should happen?
Decide whether to force the new
update.yml
workflow on all repositories in the conda org.Additional Context
No response