I use GitHub Actions to automate my development workflows, primarily focusing on tasks such as automating backups by zipping repositories and uploading them to OneDrive. Additionally, I use it for unit testing, static code analysis, software composition analysis, and automating Continuous Integration (CI) and Continuous Deployment (CD) pipelines. I also use it to deploy Docker applications to AWS Elastic Container Registry (ECR) and automate deployments with Kubernetes.
Trainee AWS Cloud Engineer at Cravita Technologies India Private Limited
Real User
Top 5
2024-10-25T09:39:00Z
Oct 25, 2024
I am currently using GitHub Actions as a tool for our CI/CD pipeline. I was engaged in an e-commerce project where I used GitHub Actions and stored secret data within GitHub Actions secrets and variables.
We mainly use GitHub Actions for our CI/CD process. Whenever there's a change in our source code, we integrate and configure it using GitHub Actions to ensure code quality before merging it into our main branch.
I use GitHub for version control. I just use GitHub repositories and GitHub Actions. I have integrated my automation project with GitHub Actions for continuous integration pipelines, allowing the team to make use of my automation scripts. It's essentially a continuous integration tool for us now.
It works excellently. Instead of having an additional CI/CD tool, we find this specific data backend tool highly beneficial. Within this data backend tool, we possess data burners, such as DNS hit creation, and within these data burners, we can conduct all build and release tasks, except for the more complicated ones like clicking. This provides a significant advantage, allowing us to automate and script processes across various environments effortlessly. I highly recommend using data backend actions for these purposes.
GitHub Actions makes it easy to automate all your software workflows, now with world-class CI/CD. Build, test, and deploy your code right from GitHub. Make code reviews, branch management, and issue triaging work the way you want.
I use GitHub Actions to automate my development workflows, primarily focusing on tasks such as automating backups by zipping repositories and uploading them to OneDrive. Additionally, I use it for unit testing, static code analysis, software composition analysis, and automating Continuous Integration (CI) and Continuous Deployment (CD) pipelines. I also use it to deploy Docker applications to AWS Elastic Container Registry (ECR) and automate deployments with Kubernetes.
I am currently using GitHub Actions as a tool for our CI/CD pipeline. I was engaged in an e-commerce project where I used GitHub Actions and stored secret data within GitHub Actions secrets and variables.
I use the platform to automate my CI/CD pipelines, specifically to deploy code once merged.
We mainly use GitHub Actions for our CI/CD process. Whenever there's a change in our source code, we integrate and configure it using GitHub Actions to ensure code quality before merging it into our main branch.
I use GitHub for version control. I just use GitHub repositories and GitHub Actions. I have integrated my automation project with GitHub Actions for continuous integration pipelines, allowing the team to make use of my automation scripts. It's essentially a continuous integration tool for us now.
One way I use it is to commit code and then take it from there to create pipelines.
I use GitHub Actions as a CI/CD tool in one of my company's projects.
We use it for the integration and release processes related to our PRCB activities.
It works excellently. Instead of having an additional CI/CD tool, we find this specific data backend tool highly beneficial. Within this data backend tool, we possess data burners, such as DNS hit creation, and within these data burners, we can conduct all build and release tasks, except for the more complicated ones like clicking. This provides a significant advantage, allowing us to automate and script processes across various environments effortlessly. I highly recommend using data backend actions for these purposes.