Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Do we remove the old sync.yml workflow? #1016

Closed
2 tasks done
kenodegard opened this issue Aug 20, 2024 · 2 comments · Fixed by #1065
Closed
2 tasks done

Do we remove the old sync.yml workflow? #1016

kenodegard opened this issue Aug 20, 2024 · 2 comments · Fixed by #1065
Labels
in-progress issue is actively being worked on source::anaconda created by members of Anaconda, Inc. type::task indicates a change that doesn't pertain to the code itself, e.g. updating CI/CQ, rebuilding package

Comments

@kenodegard
Copy link
Contributor

kenodegard commented Aug 20, 2024 •
edited
Loading

Checklist

  • I added a descriptive title
  • I searched open requests and couldn't find a duplicate

What is the idea?

Should we force all conda org repositories to use the new update.yml workflow? And then delete the old sync.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 the CODE_OF_CONDUCT.md and adding the update.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
@kenodegard kenodegard added in-progress issue is actively being worked on type::task indicates a change that doesn't pertain to the code itself, e.g. updating CI/CQ, rebuilding package source::anaconda created by members of Anaconda, Inc. labels Aug 20, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in 🧭 Planning Aug 20, 2024
@jezdez
Copy link
Member

jezdez commented Aug 21, 2024

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.

@kenodegard
Copy link
Contributor Author

Just initiated both conda-lock and grayskull

@kenodegard kenodegard mentioned this issue Nov 19, 2024
Merged
@github-project-automation github-project-automation bot moved this from 🆕 New to 🏁 Done in 🧭 Planning Nov 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
in-progress issue is actively being worked on source::anaconda created by members of Anaconda, Inc. type::task indicates a change that doesn't pertain to the code itself, e.g. updating CI/CQ, rebuilding package
Projects
🧭 Planning
Archived in project
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Remove unused sync.yml workflow kenodegard/conda-infrastructure
2 participants
@jezdez @kenodegard