Loading…
Topic
GitHub Actions
3 posts about GitHub Actions. Every summary links to the original.
- 3 posts
- 3 companies
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
Your diff has a demo now with Junie /demo
Junie /demo adds a mode to Junie CLI that builds and launches an application, drives its UI, and records a requested check. It produces an HTML report, screenshots, and video, while leaving reviewers able to inspect steps, outcomes, and evidence. In the example, a prompt selects two issues, marks them Done, checks counter changes, reloads the page, and verifies persistence. Initial setup analyzes the repository and generates configuration after a confirmed build and launch plan; Docker-based environments can use custom templates for complex repositories. The mode also supports GitHub Actions workflows for pull-request demonstrations and release smoke tests, but an explicit PASS verdict is required for a scenario to pass.
Using GitHub Actions with Heroku Flow for additional Security Control
The pattern combines GitHub Actions with Heroku Flow for private repositories and stricter security requirements when GitHub organization IP restrictions cannot use Heroku IP ranges. A custom self-hosted GitHub Runner runs as a Docker image on Heroku, while the Platform API and Source Endpoint API upload source code to ephemeral storage, build and deploy apps, and manage Review Apps. Event-specific workflows handle pushes, manual runs, schedules, and pull requests; a weekly workflow rebuilds and autodeploys the runner image within GitHub’s 30-day update window. Setup uses a Heroku Private Space, its outbound IPs, a GitHub access token, and organization name, but omits the repository URL in the Review App UI, does not run conventional Heroku CI tests, and is incompatible with Fir.
How to Create a Secure CI/CD Pipeline Using Okta Terraform
The guide presents a secure CI/CD pipeline for managing Okta resources with Terraform, AWS, and GitHub Actions, addressing local setup, collaboration, state storage, secrets, and deployment automation. Its architecture uses GitHub as source control and workflow trigger, GitHub OIDC to authenticate to AWS IAM STS and assume roles, S3 for Terraform state, DynamoDB for state locking, and AWS Secrets Manager for Okta OAuth 2.0 client credentials private keys. Developers push changes to develop for an automatic development build, open a pull request to main for a production plan, and merge approved changes to trigger the production build. The workflows run Terraform init, plan, and apply as appropriate, while the guide also covers repository setup, branch organization, and troubleshooting for missed configuration in GitHub, Okta, or AWS.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.