I've seen something like this being used to show the last X commits in a readme and I hate to be _that_ guy, but do we really need scripts that spin up a VM and install python/ruby/whatever multiple times a day just to potentially update a readme that only a few people will see?
Doing this once a week, like the article mentions, should be good enough for most people. It's not _that_ critical information.
If you want it to be very efficient, pick a language like Rust, Go, Nim, maybe even Crystal or Haskell, which can produce a (mostly) self-contained executable, without installing anything. Write the logic for updating your profile with it, all while honing your efficient coding skills.
The few people who look at your GitHub profile may be some important people, like your every future prospective employer. It may make sense to impress them a little bit.
Or you use something like this, build your blog in CI, get the top X posts in its CI workflow, and send it as JSON payload to the GitHub repository with the README you want to upload.
Your cron schedule is currently 3 times an hour. So this script ran 78840 times in three years to generate 1490 commits. So less than two percent of scheduled actions triggered a commit.
Wonder if web hooks or event driven execution might be more efficient.
A much easier way to do this (or at least to get started) is with https://github.com/muesli/markscribe - you just have to write a Go template readme.md.tpl, and run the Action on a cron and it will render it to readme.md.
The article makes it seem like there's something special about .github/scripts - but using that is if anything a bad idea, it's not special, but maybe it will be (at GitHub's discretion) in the future. There's two good points to make: 1) you can have a profile readme; 2) you might like to update it via a cron Action. But don't put your script there and all the waffle about TS and Ruby and whatever is beside the point.
Very cool. Literate programming is always an interesting exercise. In my undergrad I developed a little Julia macro library for turning my code with LaTeX encoded comments into a LaTeX document with code blocks, since the relevant source code needed to be explained as a central part of my thesis.
P.S., nice profile. Just finished reading the Landstreicher translation of The Unique and Its Property last night.
Yeah I just have a chart of potholes filled in Raleigh via python, https://github.com/apwheele. (So doesn't update the readme.md itself, just updates the PNG the readme points to.)
Good idea to add in a `timeout-minutes: 15` or something like that for the job (in case scraper code can hang). I agree it is cheeky, but I enjoy watching things I built just work over time.
Yeah I was kind of surprised to see the HTML scraping going on; if provide an RSS/ATOM feed and this task is a lot simpler, and doesn't need the overhead of Ruby (or any programming language) either, can easily be done with a bash script.
Woah, I’ve been actively using GitHub for over a decade and I had no idea it had profile pages like this if you make a repo that is the same as your username. Is this a new thing? How did I completely miss the bus on this?
This kind of activity is exactly what I hate about Github and the new and unimproved "open source community".
No one cares you updated your vimrc file. Nobody wants to see another "awesome list" in a code repository. Nobody cares about that cool project you started over a weekend and haven't touched in three years.
Your commits are not important.
We have become so narcissistic. We are now coding with the kardashians.
You can also make UIs by chopping up an image and making some of them links. Check out my profile, the buttons are clickable: https://github.com/veggiedefender
[+] [-] nikeee|2 years ago|reply
Doing this once a week, like the article mentions, should be good enough for most people. It's not _that_ critical information.
[+] [-] simonw|2 years ago|reply
That way at least the automation activity stays entirely within the GitHub / Azure network.
It looks like you can do that for Ruby by adding this:
https://github.com/actions/cache/blob/master/examples.md#rub...
[+] [-] nine_k|2 years ago|reply
The few people who look at your GitHub profile may be some important people, like your every future prospective employer. It may make sense to impress them a little bit.
[+] [-] hk1337|2 years ago|reply
EDIT
https://blog.marcnuri.com/triggering-github-actions-across-d...
Or you use something like this, build your blog in CI, get the top X posts in its CI workflow, and send it as JSON payload to the GitHub repository with the README you want to upload.
[+] [-] beebmam|2 years ago|reply
[+] [-] simonw|2 years ago|reply
https://github.com/simonw is my profile.
https://github.com/simonw/simonw/commits/main shows 1,490 commits updating my profile so far, almost all of them from the GitHub Actions automation.
[+] [-] leipert|2 years ago|reply
Wonder if web hooks or event driven execution might be more efficient.
[+] [-] slowhand09|2 years ago|reply
[+] [-] OJFord|2 years ago|reply
The article makes it seem like there's something special about .github/scripts - but using that is if anything a bad idea, it's not special, but maybe it will be (at GitHub's discretion) in the future. There's two good points to make: 1) you can have a profile readme; 2) you might like to update it via a cron Action. But don't put your script there and all the waffle about TS and Ruby and whatever is beside the point.
[+] [-] Krutonium|2 years ago|reply
[+] [-] ornornor|2 years ago|reply
[+] [-] maett|2 years ago|reply
[+] [-] stabbles|2 years ago|reply
[+] [-] bastardoperator|2 years ago|reply
[+] [-] tedivm|2 years ago|reply
* https://github.com/tedivm/
* https://github.com/tedivm/tedivm/blob/main/.github/workflows...
[+] [-] beardog|2 years ago|reply
[+] [-] OkayPhysicist|2 years ago|reply
P.S., nice profile. Just finished reading the Landstreicher translation of The Unique and Its Property last night.
[+] [-] digitalsushi|2 years ago|reply
[+] [-] pncnmnp|2 years ago|reply
Does anyone know of any other interesting ones?
Edit: I found this thread from 2021 (https://news.ycombinator.com/item?id=29248368)
[+] [-] apwheele|2 years ago|reply
Good idea to add in a `timeout-minutes: 15` or something like that for the job (in case scraper code can hang). I agree it is cheeky, but I enjoy watching things I built just work over time.
[+] [-] jamietanna|2 years ago|reply
Looking back I did it over a year ago! (https://www.jvt.me/posts/2022/01/12/autogenerated-profile-re...) I keep meaning to rewrite it because it's a set of _very_ rough Go which was some of my first Go I wrote
[+] [-] marginalia_nu|2 years ago|reply
[+] [-] wingi|2 years ago|reply
[+] [-] politelemon|2 years ago|reply
[+] [-] OkGoDoIt|2 years ago|reply
[+] [-] azemetre|2 years ago|reply
[+] [-] ethicalsmacker|2 years ago|reply
No one cares you updated your vimrc file. Nobody wants to see another "awesome list" in a code repository. Nobody cares about that cool project you started over a weekend and haven't touched in three years.
Your commits are not important.
We have become so narcissistic. We are now coding with the kardashians.
[+] [-] eat_veggies|2 years ago|reply
[+] [-] bhupesh|2 years ago|reply
[+] [-] qikInNdOutReply|2 years ago|reply
[+] [-] darekkay|2 years ago|reply
[1] https://darekkay.com/blog/github-profile-readme/
[+] [-] boredumb|2 years ago|reply
[+] [-] unknown|2 years ago|reply
[deleted]