social.coop

Frontend DogmaEleventy: A GitHub Workflow to Check if an Automated Dependency Update Would Break Your Site, by <a href="https://mas.to/@j9t" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@j9t</a> [<a href="https://mas.to/@frontenddogma" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@frontenddogma</a>]:<a href="https://meiert.com/en/blog/eleventy-github-workflow/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://meiert.com/en/blog/eleventy-github-workflow/</a><a href="https://mas.to/tags/eleventy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#eleventy</a> <a href="https://mas.to/tags/dependencies" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#dependencies</a> <a href="https://mas.to/tags/nodejs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#nodejs</a> <a href="https://mas.to/tags/automation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#automation</a> <a href="https://mas.to/tags/githubactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubactions</a>

Daniel, pined-lizard editionStatus update: I'm now automatically building and releasing a signed fork of stable moshidon with my patches. <a href="https://masto.doserver.top/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> is cool!<a href="https://github.com/cactichameleon9/moshidon-fork" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/cactichameleon9/moshidon-fork</a><a href="https://masto.doserver.top/tags/CICD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CICD</a> <a href="https://masto.doserver.top/tags/GithubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GithubActions</a> <a href="https://masto.doserver.top/tags/Moshidon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Moshidon</a>

LavX NewsRevolutionizing CI/CD: OpenHands AI Action Brings Natural Language Automation to GitHub WorkflowsThe newly launched OpenHands AI Action empowers developers to automate complex tasks within their GitHub workflows using natural language prompts. By leveraging customizable LLM models and Docker-base...<a href="https://news.lavx.hu/article/revolutionizing-ci-cd-openhands-ai-action-brings-natural-language-automation-to-github-workflows" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/revolutionizing-ci-cd-openhands-ai-action-brings-natural-language-automation-to-github-workflows</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.cloud/tags/AIAutomation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AIAutomation</a> <a href="https://mastodon.cloud/tags/OpenHands" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#OpenHands</a>

Frontend Dogma5 GitHub Actions Every Maintainer Needs to Know, by <a href="https://hachyderm.io/@github" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@github</a>:<a href="https://github.blog/open-source/maintainers/5-github-actions-every-maintainer-needs-to-know/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.blog/open-source/maintainers/5-github-actions-every-maintainer-needs-to-know/</a><a href="https://mas.to/tags/githubactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubactions</a> <a href="https://mas.to/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> <a href="https://mas.to/tags/tooling" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tooling</a> <a href="https://mas.to/tags/automation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#automation</a> <a href="https://mas.to/tags/maintenance" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#maintenance</a>

Hugo van Kemenade"GitHub Actions: macOS 15 and Windows 2025 images are now generally available" Add `macos-15` and `windows-2025` to use them. <a href="https://github.blog/changelog/2025-04-10-github-actions-macos-15-and-windows-2025-images-are-now-generally-available/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.blog/changelog/2025-04-10-github-actions-macos-15-and-windows-2025-images-are-now-generally-available/</a> <a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://mastodon.social/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.social/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://mastodon.social/tags/macOS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#macOS</a> <a href="https://mastodon.social/tags/Windows" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Windows</a>

Nicolas Fränkel 🇺🇦🇬🇪<a href="https://mastodon.top/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> by Example<a href="https://samirs-organization-6.gitbook.io/github-actions-by-example" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://samirs-organization-6.gitbook.io/github-actions-by-example</a>

Gonçalo Valério"CodeQLEAKED – Public Secrets Exposure Leads to Supply Chain Attack on GitHub CodeQL"<a href="https://www.praetorian.com/blog/codeqleaked-public-secrets-exposure-leads-to-supply-chain-attack-on-github-codeql/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.praetorian.com/blog/codeqleaked-public-secrets-exposure-leads-to-supply-chain-attack-on-github-codeql/</a><a href="https://s.ovalerio.net/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> <a href="https://s.ovalerio.net/tags/githubactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubactions</a> <a href="https://s.ovalerio.net/tags/supplychain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#supplychain</a> <a href="https://s.ovalerio.net/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://s.ovalerio.net/tags/cicd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cicd</a>

Gonçalo Valério"Whose code am I running in GitHub Actions?"<a href="https://alexwlchan.net/2025/github-actions-audit/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://alexwlchan.net/2025/github-actions-audit/</a><a href="https://s.ovalerio.net/tags/security" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#security</a> <a href="https://s.ovalerio.net/tags/supplychain" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#supplychain</a> <a href="https://s.ovalerio.net/tags/cicd" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cicd</a> <a href="https://s.ovalerio.net/tags/githubactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubactions</a>

Python Rennes<a href="https://social.breizhcamp.org/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://social.breizhcamp.org/tags/github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#github</a> il est désormais possible d'utiliser des versions "free-threaded" de <a href="https://social.breizhcamp.org/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> (sans le global interpreter lock, qui bride la façon de faire de l'exécution concurrente) dans les <a href="https://social.breizhcamp.org/tags/githubactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubactions</a><a href="https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/</a>

Python RennesNous avons tous nos bonnes pratiques lorsqu'il s'agit de créer un nouveau <a href="https://social.breizhcamp.org/tags/projet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#projet</a> <a href="https://social.breizhcamp.org/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a>, avec l'utilisation de patterns et d'outils éprouvés : lint avec <a href="https://social.breizhcamp.org/tags/ruff" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#ruff</a> et <a href="https://social.breizhcamp.org/tags/mypy" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#mypy</a>, hooks avec <a href="https://social.breizhcamp.org/tags/precommit" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#precommit</a>, tests avec <a href="https://social.breizhcamp.org/tags/pytest" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#pytest</a>, intégration continue <a href="https://social.breizhcamp.org/tags/githubactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#githubactions</a> : <a href="https://github.com/neubig/starter-repo" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://github.com/neubig/starter-repo</a> Libre à chaque personne de faire évoluer le porojet selon ses propres goûts et contraintes.

Hugo van KemenadeGitHub Actions now supports free-threaded Python!I wrote up how to add it your workflows so you can start testing free-threaded Python 3.13 and 3.14 with either actions/setup-python or actions/setup-uv.<a href="https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://hugovk.dev/blog/2025/free-threaded-python-on-github-actions/</a><a href="https://mastodon.social/tags/Python" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Python</a> <a href="https://mastodon.social/tags/FreeThreaded" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#FreeThreaded</a> <a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://mastodon.social/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.social/tags/CI" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI</a> <a href="https://mastodon.social/tags/testing" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#testing</a>

Lup Yuen Lee 李立源"If you thought <a href="https://qoto.org/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> was bad, try mixing in <a href="https://qoto.org/tags/Docker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Docker</a>"<a href="https://www.feldera.com/blog/the-pain-that-is-github-actions" rel="nofollow noopener noreferrer" target="_blank">https://www.feldera.com/blog/the-pain-that-is-github-actions</a>

The New Oil<a href="https://mastodon.thenewoil.org/tags/Coinbase" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Coinbase</a> was primary target of recent <a href="https://mastodon.thenewoil.org/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> breaches<a href="https://www.bleepingcomputer.com/news/security/coinbase-was-primary-target-of-recent-github-actions-breaches/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.bleepingcomputer.com/news/security/coinbase-was-primary-target-of-recent-github-actions-breaches/</a><a href="https://mastodon.thenewoil.org/tags/cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#cybersecurity</a> <a href="https://mastodon.thenewoil.org/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://mastodon.thenewoil.org/tags/crypto" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#crypto</a>

Christoffer S.(horizon3.ai) What to know about recent Github Actions and Apache Tomcat vulnerabilities—before you investigate <a href="https://www.horizon3.ai/attack-research/attack-blogs/critical-or-clickbait-github-actions-and-apache-tomcat-rce-vulnerabilities-2025/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://www.horizon3.ai/attack-research/attack-blogs/critical-or-clickbait-github-actions-and-apache-tomcat-rce-vulnerabilities-2025/</a>The article from Horizon3 analyzes two recent high-profile vulnerabilities: CVE-2025-30066 affecting GitHub Actions (tj-actions/changed-files) and CVE-2025-24813 affecting Apache Tomcat. Despite widespread publicity, Horizon3.ai's Attack Team found that actual exploitation risk is significantly lower than reported. For the GitHub Actions vulnerability, only one repository among 1,200 examined was exposed, with no evidence of data exfiltration. For Apache Tomcat, analysis of over 10,000 endpoints revealed no vulnerable configurations in production environments. The article emphasizes the importance of prioritizing security responses based on actual risk rather than media hype.<a href="https://swecyb.com/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cybersecurity</a> <a href="https://swecyb.com/tags/GithubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GithubActions</a> <a href="https://swecyb.com/tags/Github" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Github</a> <a href="https://swecyb.com/tags/Tomcat" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Tomcat</a> <a href="https://swecyb.com/tags/Apache" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Apache</a> <a href="https://swecyb.com/tags/Vulnerability" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Vulnerability</a>

WinbuzzerGitHub has removed a poisoned Action used in 23,000+ repos after it exfiltrated CI secrets, prompting concerns over supply chain security<a href="https://mastodon.social/tags/Cybersecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Cybersecurity</a> <a href="https://mastodon.social/tags/Microsoft" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Microsoft</a> <a href="https://mastodon.social/tags/GitHub" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHub</a> <a href="https://mastodon.social/tags/CI_CD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CI_CD</a> <a href="https://mastodon.social/tags/DevSecOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#DevSecOps</a> <a href="https://mastodon.social/tags/CyberThreats" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CyberThreats</a> <a href="https://mastodon.social/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.social/tags/Malware" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#Malware</a> <a href="https://mastodon.social/tags/CodeSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CodeSecurity</a> <a href="https://mastodon.social/tags/tjactions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tjactions</a><a href="https://winbuzzer.com/2025/03/21/github-action-breach-exposes-secrets-in-hundreds-of-repositories-xcxwbn/" rel="nofollow noopener noreferrer" translate="no" target="_blank">https://winbuzzer.com/2025/03/21/github-action-breach-exposes-secrets-in-hundreds-of-repositories-xcxwbn/</a>

Jeremy HerveIf you work with GitHub Actions and have used actions to commit to a branch, you may have run into this little problem I ran into today: automatically generated commits and events triggered by a workflow, do not trigger any workflow.In practice, that means that if you used a workflow to add a commit to your Pull Request, CI will not be triggered after that commit is pushed. All the events and CI that you would expect to see run on your Pull Request will not be triggered until your next push.This is done on purpose by GitHub, as per the docs:<blockquote>When you use the repository’s <code>GITHUB_TOKEN</code> to perform tasks, events triggered by the <code>GITHUB_TOKEN</code>, with the exception of <code>workflow_dispatch</code> and <code>repository_dispatch</code>, will not create a new workflow run. This prevents you from accidentally creating recursive workflow runs. For example, if a workflow run pushes code using the repository’s <code>GITHUB_TOKEN</code>, a new workflow will not run even when the repository contains a workflow configured to run when push events occur.<a href="https://docs.github.com/en/actions/security-for-github-actions/security-guides/automatic-token-authentication" rel="nofollow noopener noreferrer" target="_blank">Automatic token authentication</a></blockquote>A possible work-around in such cases is to use a personal access token instead of the default <code>GITHUB_TOKEN</code> to trigger events that require a token.In my situation, I am using <code><a href="https://github.com/actions/github-script" rel="nofollow noopener noreferrer" target="_blank">actions/github-script</a></code> and its authenticated Octokit client. Specifically, I use <code>createOrUpdateFileContents</code> to add a new file, commit it, and push it to the branch. <code>actions/github-script</code> allows using the <code>github-token</code> input to pass your own custom token, so I used that:<pre><code>uses: actions/github-script@v7 with: github-token: ${{ secrets.API_TOKEN_GITHUB }} script: |</code></pre>The generated commit now happens in my name, and CI events are triggered as expected by that commit. <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://herve.bzh/t/en/" target="_blank">#EN</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://herve.bzh/t/github/" target="_blank">#GitHub</a> <a rel="nofollow noopener noreferrer" class="hashtag u-tag u-category" href="https://herve.bzh/t/github-actions/" target="_blank">#GitHubActions</a>

LavX NewsCascading Supply Chain Attack Exposes Secrets in Over 23,000 GitHub RepositoriesA recent supply chain attack has compromised critical CI/CD secrets across a staggering number of GitHub repositories, revealing vulnerabilities in widely used actions. The breach highlights the inter...<a href="https://news.lavx.hu/article/cascading-supply-chain-attack-exposes-secrets-in-over-23000-github-repositories" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/cascading-supply-chain-attack-exposes-secrets-in-over-23000-github-repositories</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.cloud/tags/SupplyChainSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SupplyChainSecurity</a> <a href="https://mastodon.cloud/tags/CISA" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CISA</a>

Lup Yuen Lee 李立源Compromised `reviewdog` <a href="https://qoto.org/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> "injected Malicious Code into any CI Workflows using it, dumping the CI Runner memory containing the Workflow Secrets"<a href="https://www.wiz.io/blog/new-github-action-supply-chain-attack-reviewdog-action-setup" rel="nofollow noopener noreferrer" target="_blank">https://www.wiz.io/blog/new-github-action-supply-chain-attack-reviewdog-action-setup</a>

LavX NewsCascading Supply Chain Attack Exposes CI/CD Secrets: A GitHub Action Breach AnalysisA recent cascading supply chain attack has compromised GitHub Actions, leading to the exposure of CI/CD secrets across thousands of repositories. This incident highlights vulnerabilities in the softwa...<a href="https://news.lavx.hu/article/cascading-supply-chain-attack-exposes-ci-cd-secrets-a-github-action-breach-analysis" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/cascading-supply-chain-attack-exposes-ci-cd-secrets-a-github-action-breach-analysis</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.cloud/tags/SupplyChainSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#SupplyChainSecurity</a> <a href="https://mastodon.cloud/tags/CICDSecurity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#CICDSecurity</a>

LavX NewsWindows Server 2025 Set to Revolutionize DevOps with New Features in GitHub Actions and Azure DevOpsThe upcoming release of Windows Server 2025, scheduled for general availability on April 1, 2025, promises significant enhancements for developers using GitHub Actions and Azure DevOps. With updated s...<a href="https://news.lavx.hu/article/windows-server-2025-set-to-revolutionize-devops-with-new-features-in-github-actions-and-azure-devops" rel="nofollow noopener noreferrer" target="_blank">https://news.lavx.hu/article/windows-server-2025-set-to-revolutionize-devops-with-new-features-in-github-actions-and-azure-devops</a><a href="https://mastodon.cloud/tags/news" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#news</a> <a href="https://mastodon.cloud/tags/tech" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#tech</a> <a href="https://mastodon.cloud/tags/GitHubActions" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#GitHubActions</a> <a href="https://mastodon.cloud/tags/WindowsServer2025" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#WindowsServer2025</a> <a href="https://mastodon.cloud/tags/AzureDevOps" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#AzureDevOps</a>

Recent searches

Search options

Administered by:

Server stats:

#githubactions