Skip to content

Conversation

@ghost
Copy link

@ghost ghost commented Mar 22, 2021

Combine v2 metadata.yml values into the v3 config.json.

Note I have not touched the exercise utility which still generates
metadata.yml.

Close #1166.

Combine v2 `metadata.yml` values into the v3 `config.json`.

Note I have not touched the `exercise` utility which still generates
`metadata.yml`.

Close #1166.
@ghost ghost changed the title merge metadata remove legacy metadata.yml files Mar 22, 2021
Copy link
Member

@coriolinus coriolinus left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks fine. Did you do this by hand, or with a script? If with a script, would you post a link to a gist, or if short, just in a comment or something? I prefer to make scripts like this--even one-offs--available in the history.

@ghost
Copy link
Author

ghost commented Mar 23, 2021

Did you do this by hand, or with a script?

By hand unfortunately.

I prefer to make scripts like this--even one-offs--available in the history.

I love that strategy too. Thanks for teaching me!

@ghost ghost merged commit 86f5667 into main Mar 23, 2021
@ghost ghost deleted the close-1166-legacy-metadata branch March 23, 2021 17:43
@ghost ghost mentioned this pull request Mar 23, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[v2] metadata.yml files still needed?

2 participants