In this post, Tomas Wróbel lays out 10 potential drawbacks to the typical PR flows:
- More long living branches, more merge conflicts
- The reviewability of a change decreases with size
- Short feedback loop makes programming fun
- Reviews tend to be superficial
- Merging is blocked by remarks that shouldn’t be blocking
- It’s easier to fix than to explain the fix
- Developers are slower to adapt the responsibility mindset
- PRs discourage continuous refactoring
- Negative emotions and outright pathology
- How do you switch to branches with migrations
Samanta de Barros:
If, like me, configuring GitHub Actions is not your thing and you find yourself wanting to try something before actually pushing it to GitHub (and having to see the effects on real-life), follow this step by step of how to run your GitHub Actions on your own computer.
I wouldn’t advise obsessing over your GitHub stats, but if you’re going to do it anyway… might as well do it with this rad looking terminal UI! 😆
Enterin browser address bar for any repository you want to read. For example VS Code’s repo: https://github1s.com/microsoft/vscode
Daniel Stenberg answers critics who believe curl shouldn’t be hosted on GitHub (for various reasons) by asking himself the question: what happens if GitHub “takes the ball and goes home”?
No matter which service we use, there’s always a risk that they will turn off the light one day and not come back – or just change the rules or licensing terms that would prevent us from staying there. We cannot avoid that risk. But we can make sure that we’re smart about it, have a contingency plan or at least an idea of what to do when that day comes.
Whether or not you agree with Daniel’s GitHub-related conclusions, this statement is 💯% true and we should all be doing similar analyses before adopting any 3rd-party offering.
Okay this is pretty stinkin’ clever.
- GitHub Actions is used as an uptime monitor
- Every 5 minutes, a workflow visits your website to make sure it’s up
- Response time is recorded every 6 hours and committed to git
- Graphs of response time are generated every day
- GitHub Issues are used for incident reports
- An issue is opened if an endpoint is down
- People from your team are assigned to the issue
- Incidents reports are posted as issue comments
- Issues are locked so non-members cannot comment on them
- Issues are closed automatically when your site comes back up
- Slack notifications are sent on updates
- GitHub Pages are used for the status website
- A simple, beautiful, and accessible PWA is generated
- Built with Svelte and Sapper
- Fetches data from this repository using the GitHub API
In this episode we discuss Mislav’s experience building not one, but two Github CLIs - hub and gh. We dive into questions like, “What lead to the decision to completely rewrite the CLI in Go?”, “How were you testing the CLI, especially during the transition?”, and “What Go libraries are you using to build your CLI?”
This post by a community member from India shows how to use GitHub actions to build, push and deploy to OpenFaaS anywhere - whether in the cloud or on an RPi at home. The best part is that this is a fully multi-arch setup, and uses the new Docker buildx with GitHub Actions.
Track and vizualize your followers/notifications, your repo’s stars/forks/watchers/commits, issue states/assignees/labels, and more.
Maintaining a GitHub project with other people creates “many email notifications about various things.” But they don’t all hold the same importance. Maxime Vaillancourt shows us how to use Gmail filters and labels to better manage all the emails coming from GitHub issues, etc.
I receive many email notifications about various things that happen on there: direct requests to review a particular piece of code, feedback on pull requests I’ve opened, pull requests merged by their authors, people directly mentioning our username in a comment, issues closed by their authors, etc. I receive hundreds of emails every single week.
…using Gmail filters, we can automatically add labels to GitHub notification emails based on their content. This solution takes less than 10 minutes to implement, and the long-term return on investment is quite appreciable.
GitHub open sourced this long-lived private project. Learn about the why and how in this post…
Last week we open sourced all of GitHub’s product documentation, along with the Node.js web application that powers it. Check out our new public repository at github.com/github/docs.
This post tells the story of why we wanted to open source the docs, what tools we built and open sourced along the way, and how we worked to make the project welcoming to external contributors.
I made this to be able to open-source parts of our monorepo while keeping the rest private.
The result is a tool that allows you to have one monorepo that is the source of truth for as many other repos as you want. It could also be used to create “workspace” repos if you onboard a freelance and you don’t want to give him access to your whole mono-repo.
We are using nx as a monorepo tool, here is an example of it using the Copybara Action
Based on Google’s Copybara project.
If you haven’t given the new
gh a look since they announced the beta earlier this year, a lot has changed:
Since we released the beta, users have created over 250,000 pull requests, performed over 350,000 merges, and created over 20,000 issues with GitHub CLI.
It’s available for all major operating systems and if your development workflow goes through GitHub you will undoubtedly save some time and typing by adopting it.
Is Changelog CI a new service offering from your favorite news feed providers?! Nope!
Is Changelog CI a way to generate a changelog via carefully crafted PR titles? Yep!
Is auto-generating your project’s changelog a good idea? Maybe…
Earlier this year on February 2nd, 2020 Jon Evans and his team of archivists took a snapshot of all active public repositories on GitHub and sent it to a decommissioned coal mine in the Svalbard archipelago where it will be stored for the next 1,000 years.
On this episode, Jon chats with Jerod all about the GitHub Archive Program and how they’re preserving open source software for future generations.
Following Git 2.28’s highly sought after ability to configure
init.defaultBranch comes GitHub’s support at the platform level.
You can now set the default branch name for newly-created repositories under your username. This setting does not impact any of your existing repositories. Existing repositories will continue to have the same default branch they have now.
But even if you do nothing…
On October 1, 2020, if you haven’t changed the default branch for new repositories for your user, organization, or enterprise, it will automatically change from
Two days ago on this repo appeared on the top starred repositories first timers list on Changelog Nightly…
In this repository, you can find the official GitHub public product roadmap. Our product roadmap is where you can learn about what features we’re working on, what stage they’re in, and when we expect to bring them to you.
The roadmap repository is for communicating GitHub’s roadmap. Existing issues are currently read-only, and we are locking conversations, as we get started. Interaction limits are also in place to ensure issues originate from GitHub. We’re planning to iterate on the format of the roadmap itself, and we see potential to engage more in discussions about the future of GitHub products and features.
Leading off the updates for Git 2.28 is the highly sought after ability to configure
init.defaultBranch so folks can move from
main as their default branch name.
From Taylor Blau on the GitHub blog:
When you initialize a new Git repository from scratch with
git init, Git has always created an initial first branch with the name
master. In Git 2.28, a new configuration option,
init.defaultBranchis being introduced to replace the hard-coded term. (For more background on this change, this statement from the Software Freedom Conservancy is an excellent place to look).
Starting in Git 2.28,
git initwill instead look to the value of
init.defaultBranchwhen creating the first branch in a new repository. If that value is unset,
GitHub Sponsors is a step forward, but is far from a panacea. I propose “sponsorship pools”, an alternative approach to OSS sustainability.
I thought it’d be cool to get
mix test and
mix format running on pushes to the changelog.com repo, so I gave GitHub Actions the old college try. After (not too much) futzing around on my own, I figured I’d have more success by getting an expert to help out. Good call be me! 😆
Copy and paste this Markdown into your readme, swap the
username, and you’re up and running:
[![Anurag's github stats](https://github-readme-stats.vercel.app/api?username=anuraghazra)](https://github.com/anuraghazra/github-readme-stats)
I think we’ll be seeing many more
Dynamically generated $X for your GitHub readme repos pop up over the coming weeks.
Monical Powell has a great rundown of GitHub’s new profile readme feature. She lays out how to set up yours and then lists a bunch of creative ways our fellow devs are using theirs. Video games, GitHub Actions, and Spotify playlists abound.
This insight by Aaron Schlesinger on the latest Go Time is on point (IMHO), and realizing this relationship between the two social networks might change the way you think about code on GitHub…
I am now making more money than I’ve ever made while developing open-source software for a community that I adore. Pinch me, I’m dreaming.
Was it luck? there’s certainly been a lot of that.
Was it fate? Let’s leave religion out of this mmkay?…
Was it that the software I built was so incredibly compelling that it forced 535 people to give me at least $14/mo. to keep working on it? …I wish.
It’s more than that though. There were some key things I did along the way to get here. Let me tell you all about them.