You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have started encountering duplicates of CM automations for MLOps and MLPerf across multiple repositories, leading to conflicts in existing projects. Originally, I designed CM to avoid such duplication, fostering collaborative development and collective knowledge growth. As a solution, I was suggested to create a CM repository to aggregate various CM automations in one place to avoid breaking existing projects. I started prototyping it and it seems to be working...
The text was updated successfully, but these errors were encountered:
gfursin
changed the title
[CM/CMX] start aggregating all CM automations for MLOps and MLPerf in one place
[CM/CMX/MLOps/MLPerf] start aggregating all CM automations for MLOps and MLPerf in one place
Jan 17, 2025
We have started encountering duplicates of CM automations for MLOps and MLPerf across multiple repositories, leading to conflicts in existing projects. Originally, I designed CM to avoid such duplication, fostering collaborative development and collective knowledge growth. As a solution, I was suggested to create a CM repository to aggregate various CM automations in one place to avoid breaking existing projects. I started prototyping it and it seems to be working...
The text was updated successfully, but these errors were encountered: