No code reviews by default
At Raycast, the dev team only requests code reviews when they think it's necessary.
Read more [www.raycast.com]
At Raycast, the dev team only requests code reviews when they think it's necessary.
Read more [www.raycast.com]
For years, my team and I manually updated the changelog for our 250+ packages. Recently, we've improved how we go about this.
In this blog post, I'd like to tell you all about it.
Join 9,500+ smart developers
Get my monthly newsletter with what I learn from running Spatie, building Oh Dear, and maintaining 300+ open source packages. Practical takes on Laravel, PHP, and AI that you can actually use.
No spam. Unsubscribe anytime. You can also follow me on X.
"Freek’s newsletter is one of the best ways to stay updated with the Laravel and PHP ecosystem. It consistently highlights useful packages, tools, and ideas from the community, especially the amazing work coming from Spatie. As a Laravel developer building SaaS and web platforms, I find it extremely helpful to discover practical tools and insights that improve my development workflow."
A pretty interesting read by Kent on how he rebuilt his own site from scratch. Kent is mostly JavaScript focused, so it's good to get a perspective on which technolgies and solutions you choose with such a background.
The website certainly looks very good!
Read more [kentcdodds.com]
At work, Tim MacDonald decided to show git rebase the love it deserves with a brown bag session. He has record it, so we can enjoy it as well.
Read more [timacdonald.me]
Stefan Zweifel created a nice workflow to automatically merge dependabot PRs when all tests pass
Read more [stefanzweifel.io]
When you use software that is open source, you'll sometimes run into issues or small bugs that have already been fixed by the community in a PR or an issue, but have yet to be merged and/or released. If you're impatient and need that fix now, composer patches can be a solution for this problem.
Read more [www.rias.be]
Yesterday, GitHub launched discussions as a public beta. We've been using the feature for a couple months. In this blogpost, I'd like to share how we will use discussions for our repos.
After tweeting out a screenshot, it often get questions around which editor, font or color scheme I'm using. Instead of replying to those questions individually I've decided to just write down the settings and apps that I'm using.
As of Git 2.23 there is a way to configure a list of commits for git blame to ignore.
Read more [tekin.co.uk]
– blog.jetbrains.com - submitted by Nuno Maduro
Users of Pest will be happy to know there's now a nice plugin to improves integration in PhpStorm.
Read more [blog.jetbrains.com]
– ryangjchandler.co.uk - submitted by Ryan Chandler
A quick look at how you can configure your GitHub Actions workflows to only run when a certain phrase is present in the commit message.
Read more [ryangjchandler.co.uk]
What happens to all of those local branches after the pull request has been merged and deleted on Github?
Read more [tomschlick.com]
Matt Stauffer shows a good workflow for this.
Read more [mattstauffer.com]
– driesvints.com - submitted by Dries Vints
Dries Vints wrote a short piece on setting up a continuous delivery pipeline with Github Actions.
Read more [driesvints.com]
– tighten.co - submitted by Matt Stauffer
When getting an open source pull request, sometimes you'll need to make a change before merging. Here's how to do that.
Read more [tighten.co]
In this short post, I'd like to share how I use BetterTouchTool in my daily work.
– stefanbauer.me - submitted by Stefan Bauer
This article is the result of my 8 years of experience with PhpStorm and my best settings that make you a faster developer and let you focus more on the important things.
Read more [stefanbauer.me]
From time to time I need to remove all history from a GitHub repository, for instance right before releasing a package I've worked on in private. Sometimes I don't want people to see all mistakes I've made along the way :-).
My colleague Ruben explores the wonderful world of GitHub actions.
You can write workflows in YAML, which makes them easy to write and read. In the beta version of GitHub Actions you had to use Ocaml, which was quite hard to comprehend, and there was almost no documentation. If you were a bit frightened by the beta version, like me, then rest assured: the YAML version is easier to use, and the documentation is well written.
Read more [rubenvanassche.com]