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

Test PR - convert json files to yaml #329

Closed
wants to merge 1 commit into from

Conversation

anandhu-eng
Copy link
Contributor

The .json files are converted to .yaml using a python script and is not manually cross-checked. This is an initial test PR to check whether any workflow is breaking.

In reference to issue: #257

@anandhu-eng anandhu-eng requested a review from a team as a code owner October 3, 2024 07:59
@anandhu-eng anandhu-eng marked this pull request as draft October 3, 2024 07:59
Copy link

github-actions bot commented Oct 3, 2024

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

@gfursin
Copy link
Contributor

gfursin commented Oct 3, 2024

Hi @anandhu-eng . Just a reminder not to push it until we sync all the branches (main <-> dev <-> mlperf-inference) since it will result it a total mess. That's why we need to keep syncing all branches regularly while they are not too far away ...

@anandhu-eng
Copy link
Contributor Author

Sure @gfursin, this was a test PR and not meant for merging. Let me close this PR and open a new one.

@anandhu-eng anandhu-eng closed this Oct 3, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Oct 3, 2024
@gfursin
Copy link
Contributor

gfursin commented Oct 3, 2024

No worries @anandhu-eng - I saw that it was a test PR and it was just reminder to sync all the branches before changing json to yaml. It will also allow me to merge changes from flexaihq/cm4mlops before such a change to avoid breaking projects. Thanks a lot!

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.

3 participants