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.

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

Sync with dev (new) #31

Closed
wants to merge 1 commit into from
Closed

Sync with dev (new) #31

wants to merge 1 commit into from

Conversation

arjunsuresh
Copy link
Contributor

No description provided.

@arjunsuresh arjunsuresh requested a review from a team as a code owner April 30, 2024 20:47
Copy link

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

@arjunsuresh
Copy link
Contributor Author

arjunsuresh commented Apr 30, 2024

@gfursin This PR looks fine. Once merged, we can rewrite the history removing large blobs. Without history it is (saved here )

arjunsuresh@Arjuns-MacBook-Pro cm4mlops_temp % du -sh
 12M	.

With history it is currently around 40M. It can be made to <20M once we remove some large files from the git history. Anyway I don't think we need to worry about git history (unless it is huge) when talking about repo size as usually we talk about the "zip download" excluding the history.

Also, the new main/dev branches might have some files/folders that were deleted in the new cm4mlops repository. So, these need to be redeleted - I see the tests folder in the root directory that needs to be deleted.

@arjunsuresh arjunsuresh deleted the dev_temp branch April 30, 2024 22:35
@github-actions github-actions bot locked and limited conversation to collaborators Apr 30, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant