New Year, New Commitments, and New Actions 🏁

[Akash1134]

Hello everyone! 👋 and welcome to the first Action-packed check-in of 2023. Our feature list is getting stronger each day and you don’t wanna miss out on what I’ve for you today.

💌 From the Community - Shoutout 📢 to these members

Before diving into the feature list, let us thank these community members for sharing their knowledge. .

• @shirady posted a problem that they thought is a bug. @Simran-B helped with them by providing documentation and resolving the issue. 👏
• @david-engelmann was trying to upgrade an action to run on different OS's but it returned an error. ChristopherHX emulated and diagnosed the issue with perfection. Well done!
• Round of applause for these self-solvers ✅
  • @sagikazarmark quickly realized they need to add package write permissions to their workflow to be able to push the action to the container registry. Thanks for updating the [discussion(https://github.com/orgs/community/discussions/44651) with your findings. 💗
  • @Rptb1 couldn’t get their workflow running but found out the root cause and also shared important UI feedback. 👍
  • This research driven self-solve from @kirillmorozov is phenomenal.They deserve a pat on the back for updating the discussion and sharing a workaround for anyone else who might run into a similar issue.
  • Here’s another thorough investigation 🔍 by @jgillick that helped them figure out how to generate a URL to a PR file using GitHub Actions.

From the Release Radar 🚨 - Actions and Packages

Push Notifications for Actions on Mobile 🆕

Our team has introduced the new push notifications for Actions on Mobile! You can now get notified when your workflow runs have succeeded or failed on the go. Please test it out and let us know what you think.

Configuration variables in workflows - Now Supported!

GitHub Actions now support configuration variables that allow you to store your non-sensitive data as plain text variables that can be reused across your workflows in your repository or organization. This way you can define variables at Organization, Repository, or Environment level based on your requirement.

Org-wide required workflows (public beta) - Further reducing duplication of CI/CD config code ♻️

If you’re an organization admin, you can easily configure required workflows to run on all or selected repositories within the organization.

This allows your organization to be more secure 🔒 , code-complaint, and better with code deployment. For details, learn more about required workflows.

Fine-grained permissions and organization-level publishing - GitHub Packages 🧑‍💻

With an all-new architecture GitHub Packages RubyGems registry can publish packages at an organization level with the ability to invite other users to access the package.

Calling Enterprise Admins: Get $100 for sharing about your GitHub experience! 🤝

If you are an Enterprise Admin, our customer experience team would love to know about your experience with GitHub using this short survey. Please check out this post by @gennyburleson for details.

That's all for now folks. Got feedback or feature requests for anything Actions and Packages? ❓Post them on community and share enhancements you’d like to see on these products. Till next time! 🚀