bogdanp / awesome-advent-of-code Goto Github PK

MichalMarsalek/Advent-of-code should be removed from Python for 2022 since it only contains solutions in Nims for that year.

Hello 👋

Feel free to add mine to the python solutions if you see fit
https://github.com/sergiomartins8/advent-of-code-2020

Cheers!

Currently, someone who looks for a repository in a certain language will overlook the ones in the polyglot section. Marking them with the languages isn't a good solution because you have to look in two sections for it.

I suggest removing the restriction of not being able to add our codebases into multiple language sections.

Only 2018 and 2019 is there currently!

Great ressource!

maybe you would like to join us or link to us:

https://aoc-2019.netlify.com

I use Node JS for mine. I am setting up my repo it is https://github.com/TolleyB-J/AdventOfCode2018. Please add it to the list

How do you decide what repos go up here?

Looks like the new badge automation I wrote is hitting secondary rate limits:

https://github.com/Bogdanp/awesome-advent-of-code/actions/runs/8776567228
https://github.com/Bogdanp/awesome-advent-of-code/actions/runs/8592640932

When I get some time I'll have a look.

I think the badges should be updated more often because I for example uploaded my solution already, but the cron job for the update will run the next time in around 18 hours, so for 18 hours now the badge is wrong. Maybe update them every hour?

The awesome and the popular generic adventofcode topic/tag should be added to this repository, so it can easily be found on the awesome page here: https://github.com/topics/awesome

Because the default last-commit badge will format the date as December with the time changes, it is hard to distinguish between repositories now.

I find http://shields.io supports dynamic badges, which means we can design own date format. For example, YYYY/MM/DD should be better.

What's more, after badges/shields#2473 is merged, we can customize everything besides badge text.

https://github.com/misiakw/AoC/tree/main/AoC-2021

my main repo may contain other languages (i know last year i tried python for example) but this year's solution is in C#

see: 9bbfb5f#diff-b335630551682c19a781afebcf4d07bf978fb1f8ac04c6bf87428ed5106870f5L373-R373

The bot seems to replace any link to gitlab (probably any other hoster too?) with Github, thus effectively breaking external repo urls. This doesn't seem like it should be expected behaviour.

I haven't looked into the action code yet, but I guess it's somewhere in there.
I'd suggest either changing that, so the bot doesnt change urls, or not allowing external repos.

Hi folks,

Thanks for the amazing effort around this repository. As a builder of Advent of Frontend I wanted to ask if you'd be interested in featuring community projects like mine.

Feel free to share honest feedback - I don't want to force any PR if you think it's not the right idea.

Cheers

I hesitated to create fresh pre-2018 .md files because there might be a build action or specific gotcha in creating one? If there isn't, I'd be happy to create a base file for those earlier years, same setup as the newer ones?

Thx for a great repo!

Original url for every non-github repo got replaced by "http://github.com/..."

For some reason, I can't see my name/badges in the readme.md. It seems that my entry was overwritten.

I am afraid the repository misses advent-of-code-2022 and advent-of-code-2023 topics

(I know there is a previous issue on this but it was closed a year ago)

How about multi-year repositories? Or people who participate later? The last commit is good to see if something is actively developed or not, but not for progress. The most straightforward solution as mentioned before would be to allow for PR's about updating progress. But, it does have the cost of having to merge a lot of requests.

I have a far better solution that requires no maintenance other than solvers updating their own repositories:

Shields.io provides a service where you can feed it a JSON endpoint with a certain schema that will show you a custom badge. And guess what, we can use raw.githubusercontent.com as an API for this.

When pointing to a nonexistent endpoint it looks ugly (
) so I'd only add it using PR's, but one PR is still far better than any solutions before and can be added with the initial one if we let the contributor know about it.

Proof of concept:

The way I'd do it is (as seen as the previous example) is by placing a badges folder in a "hidden" folder (I'd use the existing .github folder, but a .aoc or a straight-up .shields or .badges folder, without an inner badges would be good too) and placing a <year>.json file inside which would then contain the response to render the badge:

{
	"schemaVersion": 1,
	"label": "AoC 2018",
	"message": "14/25",
	"color": "orange"
}

I'd reserve "color": "green" for completed years.

This way everybody could just update their progress inside their repositories so there's no need for any PR's except the initial one.

Ps.:

This solution would require some discipline though but I think in this community we can count on that. Especially because we only have to care about a niche sub-community of the ones who'd like to show their work. An additional disclaimer in the readme.md would be nice too, something on the line of "We do not take responsibility for the content of custom badges".

Edit: This idea then could be extended to provide information about the languages used.

It seems that my last commit badge is not updating for some reason:

The update-badge action is failing on nondescript API errors.

https://github.com/Bogdanp/awesome-advent-of-code/actions/runs/8972860331
https://github.com/Bogdanp/awesome-advent-of-code/actions/runs/9055280378
https://github.com/Bogdanp/awesome-advent-of-code/actions/runs/9151576840

When I have time I'll make the request timings more conservative and implement some form of retrying on error.

Not sure if this is intended or not, but it seems the action to update commit badges is only working on the repos for current year in README.md. If you have a look in 2022.md for instance there are several entries without badges.

Maybe a little hard. But I doubt every added project can reach 50 stars at last. Without tracking, this repository will become a list like Github search results. Not awesome.

Is there any interest in expanding the archives to contains lists of solutions for 2015, 2016, and 2017?

Can I add myself as a contributor to the CONTRIBUTORS.md for adding my repo or that's for something else? Not clear since it has only two contributors.