search

gbdev / gbdev.github.io

gbdev institutional website: showcases projects and hosts some community content
https://gbdev.io
GNU General Public License v3.0
22 stars 12 forks source link

Automate the merge from the List #8

Open avivace opened 4 years ago

avivace commented 4 years ago

This has been done manually, as a proof of concept. It should be trivially implementable.

ISSOtm commented 2 years ago

What needs to be done?

avivace commented 2 years ago

What needs to be done?

The list in this repository is based on the README.md in the awesome-gbdev, but a lot of custom elements are added, such as the video players, the "info" message about the disambiguation GB/GBA etc...

We would need some way to template the base list and "render" it into this way, possibly with commented lines so the one in the awesome-gbdev remains clean (this pontential solution is mentioned in https://github.com/gbdev/awesome-gbdev/issues/203)

ISSOtm commented 2 years ago

The Markdown could be parsed into a list of lists (categories of entries), and that processed somehow. Replacements like "insert this between category X and Y", "process entry E thusly", etc.

avivace commented 2 years ago

The Markdown could be parsed into a list of lists (categories of entries), and that processed somehow. Replacements like "insert this between category X and Y", "process entry E thusly", etc.

It's an interesting proposal, thanks ISSO. For sure better than keeping unrelated code in the source list (even if commented).

Considering our list is linted by awesome-lint (actually our version of it: https://github.com/gbdev/list-linter) it's already consistent to the point we could do that, but there's still a lot of spare and custom text around that would make it fail.

ISSOtm commented 2 years ago

I'd suggest trying to go at it anyway, and seeing what hurdles come up. It may be possible to simply ignore these elements, pass them through without any processing, or give them some special treatment as with the rest, for example.

avivace commented 2 years ago

I'd suggest trying to go at it anyway, and seeing what hurdles come up. It may be possible to simply ignore these elements, pass them through without any processing, or give them some special treatment as with the rest, for example.

Ok, but it would be super low priority for me, as manually merging the list is not a big deal anyway and it happens once(maybe twice) a year. Ping me if you have time for tests