Skip to content

Commit 642724a

Browse files
iBotPeachesCopilot
andauthored
chore: Apply suggestions from code review
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
1 parent 3a5ca61 commit 642724a

File tree

1 file changed

+2
-2
lines changed
  • blog/2025/2025-06-10-our-github-actions

1 file changed

+2
-2
lines changed

blog/2025/2025-06-10-our-github-actions/index.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ However, from our audit perspective it felt a bit weird that we were committing
2727
2828
We learned pretty quickly that GitHub offered 3 different forms of actions with them being Docker, JavaScript and Composite. We knew as another need arrived for custom code we would move away from the JavaScript based actions and instead use a Docker based one.
2929
30-
As we were trying to replicate a Jenkins plugin for AWS CodeDeploy we couldn't find anything official that AWS or the community offered to replace that Jenkins plugin. The way it worked was archiving a folder, uploading it to S3 and preforming a deployment while monitoring the progress.
30+
As we were trying to replicate a Jenkins plugin for AWS CodeDeploy we couldn't find anything official that AWS or the community offered to replace that Jenkins plugin. The way it worked was archiving a folder, uploading it to S3 and performing a deployment while monitoring the progress.
3131
3232
At the time there was no comparable action that did all those things together. We had to be responsible for creating an archive, uploading it to S3 and then calling a deployment command that didn't really offer much detail in terms of monitoring the deployment.
3333
@@ -105,7 +105,7 @@ This development of GitHub Actions continued when we found a need to build Tizen
105105
author-password: ${{ secrets.TIZEN_AUTHOR_KEY_PW }}
106106
```
107107

108-
We had a developed a pattern that when we needed to fully automate our deployment procedure and an option didn't exist. We wrote one in Bash for GitHub Actions and open sourced it. Over the years that led to the creation of:
108+
We had developed a pattern that when we needed to fully automate our deployment procedure and an option didn't exist, we wrote one in Bash for GitHub Actions and open sourced it. Over the years that led to the creation of:
109109

110110
* [ssh-socket-action](https://github.com/sourcetoad/ssh-socket-action) - A GitHub Action to set up (or reuse) an SSH socket using a private key, allowing subsequent workflow steps to perform SSH operations securely
111111
* [aws-codedeploy-action](https://github.com/sourcetoad/aws-codedeploy-action) - A GitHub Action to package and deploy applications to EC2 via AWS CodeDeploy, handling S3 upload, revision registration, and deployment monitoring

0 commit comments

Comments
 (0)