If the heading of a previous release in the changelog has a link to a compare view, the Action will use that URL and add a link to the updated compare view to the new release notes.
It's hard to explain this with words. The attached screenshot gives you a good example.
This previously only worked, if the changelog had a "Unreleased" heading with a link in it.
The past 2 weeks have been spent learning how to migrate #GitHubActions to Azure, using a well formed and functional GitHub Action yaml file. A mountain of learning, but slowly getting there. Linux builds were surprisingly simple to migrate. Hey, windows should be easy since Microsoft owns it all right? Windows builds have been anything but simple to get going on Azure.
Any #Azure#DevOps folks, happy to pay for some time to learn how to build azure-pipeline.yml files for Windows builds.
Now that @github Actions supports macOS M1 runners, we've added them to the CPython CI, and have finally promoted aarch64-apple-darwin to the top support tier!
This means CI failures block releases, cannot be merged to main or must be fixed or reverted immediately, and the whole core dev team is responsible rather than one or two.
With the inputs of GitHub actions, if you bind it the checkout action, your manual triggers could be as flexible as you want.
Example is to show how flexible this can be. In the image, I can use the workflow chore/branch, and deploy the codes in the main branch to the staging env.
increasingly heavy software ("just run these docker containers!"),
promise of free crypto "money".
People will use "Free" cloud hosting via Travis/GitHub/Circle and other CIs to run the most compute possible, triggered via random empty commits and such. This is the new normal.
It does not count as a presentation if you don't have at least one Will Ferrel gif 😆
My second talk from the Øredev conference about productionize an open source project with Docker 🐳, Github Actions, and other tools is now available 👇🏼
CI jobs for my ansible playbook have been broken for months due to some changes with GitHub Actions.
This took me down a rabbit hole to fix...
Long story short: Self-Hosted GitHub Actions runner, running on Proxmox with nested virtualization to run molecule tests using Vagrant against VirtualBox VMs. 🙃
(1/7)There is no better way for me to summarise the year than my Github account and my Git commits 😎
In 2023, I had more than 2500 commits, most related to project automation with Github Actions ❤️. Most of my personal projects during 2023 were related to tutorials and open-source projects. Here are the main highlights 🧶🧵👇🏼
Anyone know how to make this left hand jobs list in GitHub Actions wider, so I can actually distinguish which job is which please? 🤔 #github#githubactions#ui
"You basically have a couple of days to make sure that your library will have no hiccups when Python 3.12 ships in a week. You want to make sure that your stuff just works, so here's your chance and a few steps on how to do that."