GitHub discussions are now in public beta
Here's a list of things announced at the GitHub event earlier this month.
Read more [github.blog]
Here's a list of things announced at the GitHub event earlier this month.
Read more [github.blog]
Earlier this year, Travis CI announced a new pricing model that effectively ends the generous open-source offering they had for many years. It seems that, even though there were some plans to provide free resources for OSS projects in the future, all activity for OSS projects has stopped.
At our company, we create a lot of open-source projects and packages. Beginning 2020, we already moved most of our stuff to GitHub actions.
Sure, you can read the GitHub actions docs to start learning the possibilities, but in my experience, it might be better to see some examples of practical uses cases. Here are some interesting links that might help you get started with GitHub actions.
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.
"Always fresh, useful tips and articles. Carefully selected community content. My favorite newsletter, which I look forward to every time."
Here's the recording of Laravel Worldwide Meetup #4. Ryan Chandler showed a cool GitHub Action workflow to test a Laravel app. Next, Liam Hammet demonstrated some unconvential things you can do with PHP autoloaders.
A nice, concise post by Sindre Sorhus on when to issue bump and when not to.
Read more [blog.sindresorhus.com]
On our site you'll find the documentation of our bigger bigger packages, like laravel-medialibrary, laravel-backup, laravel-event-sourcing, ... Let's take a look at how that works.
– 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]
– fidum.uk
Dan Manson explains how you can run that shiny new schema:dump command on GitHub actions. Pretty cool
Read more [fidum.uk]
Sebastian show a few cool things you can do when comparing changes in the GitHub UI
Read more [sebastiandedeyne.com]
Monica Powell explains how to customize your GitHub profile page.
Read more [www.aboutmonica.com]
Recently we started using GitHub Actions to test all our packages. You can read more about our general setup in this blog post.
For most of the packages, this works great. However, some of our packages, such as Laravel Tags, use JSON functions that are not available in SQLite. Luckily it's straightforward to use a database like MySQL in GitHub Actions.
– 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]
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 :-).
For many years we've relied on Travis to run the tests of our packages. For projects we used Circle CI. Recently we moved this responsibility from Travis and Circle CI to GitHub actions. In this blogpost I'd like to explain why and how we did this.
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]
Mattias Geniar explains how you can use GitHub actions to run the testsuite of your Laravel app.
Last year we wrote a blogpost about our setup we use for Oh Dear! with Gitlab, and how we use their pipelines for running our CI tests. Since then, we've moved back to Github since they introduced their free private repositories. In this post I'll describe how we re-configured our CI environment using Github Actions.
Read more [ma.ttias.be]
Stefan Zweifel shared his GitHub action that can automatically fix code style issues using prettier and php-cs-fixer
One workflow is really like, is to run prettier and php-cs-fixer to automatically format my code and commit the fixed files back to the repository.
Read more [stefanzweifel.io]
Roberto B wrote a good tutorial on how to test your Laravel 6 application using GitHub actions.
The scenario that I would like to explain you is: I have a Web App based on Laravel 6, every time I push some new code on master branch on the GitHub repository, I would like to execute automatically Unit tests and Feature tests.
Read more [medium.com]
Here’s another: see the public keys of a github user by adding ‘.keys’ to their profile URL:
— Bramus! (@bramus) January 23, 2019
? https://t.co/GaHnUISqM1
? https://t.co/zIeqVbxQbE
Read more [twitter.com]