#typescript #github_actions #github_releases
This GitHub Action helps create and manage GitHub Releases automatically. It supports Linux, Windows, and macOS environments. You can use it to limit releases to specific tags, upload release assets, and include external release notes. Customization options allow you to control the release name, notes, and whether it's a draft or prerelease. This automation saves time and ensures consistency in your release process, making it easier to manage software deployments efficiently.
https://github.com/softprops/action-gh-release
This GitHub Action helps create and manage GitHub Releases automatically. It supports Linux, Windows, and macOS environments. You can use it to limit releases to specific tags, upload release assets, and include external release notes. Customization options allow you to control the release name, notes, and whether it's a draft or prerelease. This automation saves time and ensures consistency in your release process, making it easier to manage software deployments efficiently.
https://github.com/softprops/action-gh-release
GitHub
GitHub - softprops/action-gh-release: 📦 GitHub Action for creating GitHub Releases
📦 :octocat: GitHub Action for creating GitHub Releases - softprops/action-gh-release
#go #github_actions #kubernetes #operator
Actions Runner Controller (ARC) is a tool that helps you automatically manage and scale self-hosted GitHub Actions runners using Kubernetes. It creates runner scale sets that grow or shrink based on how many workflows you are running, making your CI/CD process more efficient and cost-effective. ARC uses containers for runners, so new instances can start or stop quickly and cleanly. You can install ARC easily with Helm on Kubernetes and customize runners with features like custom images, volumes, and scripts. This automation saves you time and resources by matching runner capacity to your actual workload needs[1][2][3].
https://github.com/actions/actions-runner-controller
Actions Runner Controller (ARC) is a tool that helps you automatically manage and scale self-hosted GitHub Actions runners using Kubernetes. It creates runner scale sets that grow or shrink based on how many workflows you are running, making your CI/CD process more efficient and cost-effective. ARC uses containers for runners, so new instances can start or stop quickly and cleanly. You can install ARC easily with Helm on Kubernetes and customize runners with features like custom images, volumes, and scripts. This automation saves you time and resources by matching runner capacity to your actual workload needs[1][2][3].
https://github.com/actions/actions-runner-controller
GitHub
GitHub - actions/actions-runner-controller: Kubernetes controller for GitHub Actions self-hosted runners
Kubernetes controller for GitHub Actions self-hosted runners - actions/actions-runner-controller
#typescript #actions #authentication #gcp #github_actions #google_cloud #google_cloud_platform #iam #identity #security
You can securely connect GitHub Actions to Google Cloud using the Google GitHub Action called `auth`. It supports two main ways: the recommended Workload Identity Federation (WIF), which uses short-lived tokens and avoids long-lived service account keys, and the older Service Account Key JSON method. WIF improves security by creating a trust link between your GitHub workflow and Google Cloud without exposing permanent credentials. To use it, you set up a Workload Identity Pool and Provider in Google Cloud, then configure your GitHub workflow to authenticate with these. This lets your workflows access Google Cloud resources safely and easily, reducing risks and simplifying credential management.
https://github.com/google-github-actions/auth
You can securely connect GitHub Actions to Google Cloud using the Google GitHub Action called `auth`. It supports two main ways: the recommended Workload Identity Federation (WIF), which uses short-lived tokens and avoids long-lived service account keys, and the older Service Account Key JSON method. WIF improves security by creating a trust link between your GitHub workflow and Google Cloud without exposing permanent credentials. To use it, you set up a Workload Identity Pool and Provider in Google Cloud, then configure your GitHub workflow to authenticate with these. This lets your workflows access Google Cloud resources safely and easily, reducing risks and simplifying credential management.
https://github.com/google-github-actions/auth
GitHub
GitHub - google-github-actions/auth: A GitHub Action for authenticating to Google Cloud.
A GitHub Action for authenticating to Google Cloud. - google-github-actions/auth
#go #actions #cai #ci #claude_code #codex #copilot #gh_extension #github_actions
GitHub Agentic Workflows let you write simple markdown instructions in natural language to automate repo tasks like triaging issues, fixing CI failures, generating reports, and improving code—running safely as GitHub Actions with AI like Copilot or Claude. Strong guardrails ensure read-only access by default, sandboxed execution, and human-reviewed outputs via pull requests. This saves you time on repetitive work, boosts efficiency with adaptive AI decisions, and keeps everything secure without complex YAML coding.
https://github.com/github/gh-aw
GitHub Agentic Workflows let you write simple markdown instructions in natural language to automate repo tasks like triaging issues, fixing CI failures, generating reports, and improving code—running safely as GitHub Actions with AI like Copilot or Claude. Strong guardrails ensure read-only access by default, sandboxed execution, and human-reviewed outputs via pull requests. This saves you time on repetitive work, boosts efficiency with adaptive AI decisions, and keeps everything secure without complex YAML coding.
https://github.com/github/gh-aw
GitHub
GitHub - github/gh-aw: GitHub Agentic Workflows
GitHub Agentic Workflows. Contribute to github/gh-aw development by creating an account on GitHub.
👍2❤1