Building a self-updating profile README for GitHub
simonwillison.net
simonwillison.net
Two of my favourites:
Zhi Yang built one which fetched their latest tweet, renders it to a PNG using headless Chrome (from an R script) and adds it to her profile: https://github.com/zhiiiyang
Katie McLaughlin built one that does an ASCII art render of her profile: https://github.com/glasnt
I'm collecting these in a Twitter thread as I spot them: https://twitter.com/simonw/status/1281435464474324993
Started collecting some of those examples here:
1. You can schedule workflows. This is super useful for running dependency vulnerability scanners on repos that don't see active development.
2. You can manually trigger workflows. This is perfect for one repo I have where I manually build releases. The branching model doesn't lend itself well to a PR release action, and the need for inputs complicates things further. But now I can move the release infrastructure off of my laptop and into GitHub Actions.
It's just XML so it's really simple (here's the webring thing, if you want to see for yourself: https://github.com/pmn/randos.online)
Next stop for Microsoft: Add your real LinkedIn profile. What could possibly go wrong?
Neither of these places will find you every possible developer
Maybe its not a problem for microsoft to be using the multiple channels available to them to diversify and extend their reach.
[1] https://www.w3schools.com/howto/howto_css_table_responsive.a...
It is a github profile, after all. A personal webpage is better for all the other information about you, and you can just put that link in your profile description.
I'm lightly skewing towards just hiding it with a custom rule and forget about them. I visit a Github profile to quickly see what the developer codes instead of a showcase of their personality which, as you said, would be better served by a personal website.
I'm already amazed by the different profiles I've seen so far.
Edit: Include the image with html in Markdown, so <img src="..." align="left">.
Get your Github repositories to that state.
Also nice to see this new hack using GitHub actions to keep the current updated. Here is my profile README (kept it simple), love to see others as well: https://github.com/suyashjoshi
Now, we can discuss about whether or not that's a good thing and the quality of the kind of contributions you tend to get because of the lower barrier but GitHub, at least currently, still has a place in the workflow of a lot of people.
What you propose would also be really awesome. A feature like this in Gitea could be really nice. If you'd like, you can open an issue on the Gitea issue tracker [1] for the feature.
Microsoft with features like these, acquiring NPM etc. and more to come, will be 'the Google of the dev world' (or they already are). Locked-in by the platform and by FOMO we'll be. And Gitea and other such fine works only used in the fringes of software development is my fear.
Big tech is causing big problems, as often discussed on HN. In this domain there are still competitors that can pick up the glove and put up a real fight. Gitlab can, but Gitea could do too. And imho here's how:
Federated forges, by adopting ActivityPub-based ForgeFed protocol [0]. I've searched your issue tracker and see [1] you are already considering adoption of parts of it.
I think federation support will greatly boost the attractiveness of Gitea as an alternative to GH.
PS. I've also heard talk to create federated LinkedIn alternatives.
Besides, I don’t know that either GitLab nor Gitea has the kind of feature with profile README that is mentioned in the submitted link.
a feature i love about github desktop is auto-generated commit messages. some commit messages are not worth spending time on. and yet people insist on us wasting time writing them. github desktop makes me extremely happy with these "boring" but so useful messages.
auto-generated commit messages are the best things any git client has ever done!
hoping that the team will continue to work on that feature. in fact, i would love to not have have to write a single commit message except for merges, amending, and pull requests.