Take Action this April! [Actions Check-in]

[grandmas-favorite]

Hello Community! 👋

Spring is here and the weather’s warming for those in the Northern Hemisphere, so it’s time for another Actions check-in!

The first few months of 2024 have been wonderfully busy for the Actions category, which makes it especially difficult to narrow down the list of notable community contributors since last check-in! 🚀

That said, take a look below at some of the key contributors from March:

• @Sule26 helped out @YaronPeres when they got stuck trying to use Actions to push files from their main branch to their deploy branch. @Sule26 came to the rescue and offered a script that got the push working! 👏

• Shout out to @oerp-odoo for helping themselves out with a beautiful self-solve. They found a workaround for an unexpected behavior in their auto-merge job, and swung back to the Community to post it so that others can learn from it too! Bravo! 🏆

• When @teodik needed help creating a variable in one job and using it in other jobs, they extended their hand out to the Community and @weitsunglin came to their aid. These two had a 7-reply exchange before they finally got it figured out! Hats off for this incredible display of Community 🎉

If you love open source like we do, you can always contribute directly to any doc by submitting a PR, learn more about how to contribute to GitHub docs. 📝

What’s the latest in Actions? 🆕

Hardware accelerated Android virtualization now available!

Actions users of our 2-vCPU GitHub-hosted Linux runners will now be able to make use of hardware acceleration for Android testing. Previously, this feature was only available on runners with 4 or more vCPUs. For more information on how to set-up hardware acceleration, please see our documentation.

Actions Usage Metrics public beta has arrived!

In case you missed it, Actions Usage Metrics public beta has arrived! ,Actions Usage Metrics addresses the question of “where are all of my minutes going?” and many others by focusing on minutes used per workflow, job, repository, runtime OS, and runner type. Check out our docs here, and head over to the Community thread to give your feedback.

Important dates to save

A few Deprecation notices next. Firstly, Starting November 30, 2024, GitHub Actions customers will no longer be able to use v3 of actions/upload-artifact or actions/download-artifact. Please see the documentation in the project repositories for guidance on how to migrate your workflows.

Also, From the 15th of May 2024 we will no longer support multiple labels on larger GitHub Hosted Runners. We will be running a brown out on the 8th of May between 18:00 and 20:00 UTC, during this time multi label larger runner jobs will fail to start. To prepare for this change and avoid any disruption, please ensure the runs-on: references only the runner name in your workflows prior to the dates above.

In case you missed these GitHu-pdates…

• Github Universe 2024 tickets are now on sale! As the world’s fair of software, GitHub Universe 2024 will be an unparalleled gathering of the brightest minds, companies, and innovators in the industry. With sessions diving into AI, the developer experience (DevEx), and security, attendees will have an opportunity to explore the latest products, best practices, and insights shaping the future of software development.

  - Get tickets 35% off here only from now until July 8!

• Show everyone that you’re a GitHub expert with our GitHub Certifications, now generally available. What was once reserved for employees and partners is now available to anyone who wants to prove their GitHub wit! 📜

What are you most excited about for the months of April and May? Comment or share a reaction below!