While GitHub Actions offers a range of functionalities, it is newer compared to more established tools such as Jenkins and Azure DevOps. There is still room for improvement, especially in areas concerning deeper capabilities akin to those provided by Jenkins and Azure DevOps. Given the evolving nature of technology, there are potential improvements GitHub Actions can focus on, including enhancing support and reliability to match its competitors.
Frankly, I cannot imagine something that could be improved in GitHub Actions; there's a lot of capabilities, and the feature set is more advanced than we use. The pricing is high for the advanced security; GitHub Advanced Security for us is quite pricey.
Chief Technology Officer at Teslon Technologies Pvt Ltd
Real User
Top 20
Apr 4, 2025
I would need to check with my team about specific shortcomings. We still use Jenkins ( /products/jenkins-reviews ) for some tasks, which suggests there may be areas for improvement in GitHub Actions.
GitHub Actions lacks a feature for automating the build process for mobile applications. I currently rely on GitHub Actions for web applications but have to use another tool for mobile apps.
The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket. I had to conduct extensive research to find a solution using RClone for configuration. Focusing on making integrations smoother would be beneficial.
The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these artifacts is complex. Simplifying this process would make GitHub Actions even more user-friendly and efficient. Other than this aspect, GitHub Actions stands out as an excellent tool for automating and managing workflows. For additional functionalities, one aspect I'd like to see improved is the integration of performance testing and API automation projects directly within GitHub Actions, without the need for third-party tools. This direct integration would streamline the process significantly.
Business Mobility Development (AVP-BMD) at SC Asset
Real User
Nov 21, 2023
I feel that the product is okay for me. Sometimes, it takes a while to deploy the product. Some of the functions of the product are hard to understand owing to its scripts or UI. The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly.
While our current pipeline handles most of the deployment, we believe there's room for improvement, especially when it comes to generating comprehensive reports and metrics. The reporting capabilities are somewhat limited.
it specialist at a tech services company with 10,001+ employees
Real User
Top 5
Aug 31, 2023
We can leverage this database tool to manage everything within our environment and data burners, allowing for customization and execution. An additional advantage is the capability to modify aspects like file size, making processes more efficient and faster across the pipelines. Regarding improvements or implementations, I believe there should be enhancements made to the deployment tool. It should be integrated as part of the solution. Infrastructure-wise, we already have tools like GitHub and RobSpot, and data enables us to automate various processes, which is quite beneficial. As for further enhancements, I'm uncertain. I've shared everything I know. However, if there's something specific you'd like to see in future releases, a feature that may not exist yet but would be desirable, I can't provide any input on that matter.
GitHub Actions streamlines CI/CD processes with an intuitive YAML workflow and robust automation, enhancing efficiency and integration with third-party tools and cloud providers.GitHub Actions automates development pipelines, supports scalable public and private runners, and manages secure secrets. This tool integrates seamlessly with platforms like AWS, Kubernetes, Google Cloud, and Databricks. It enhances DevOps workflows with reliable task automation. Users note areas for UI and deployment...
While GitHub Actions offers a range of functionalities, it is newer compared to more established tools such as Jenkins and Azure DevOps. There is still room for improvement, especially in areas concerning deeper capabilities akin to those provided by Jenkins and Azure DevOps. Given the evolving nature of technology, there are potential improvements GitHub Actions can focus on, including enhancing support and reliability to match its competitors.
Frankly, I cannot imagine something that could be improved in GitHub Actions; there's a lot of capabilities, and the feature set is more advanced than we use. The pricing is high for the advanced security; GitHub Advanced Security for us is quite pricey.
I would need to check with my team about specific shortcomings. We still use Jenkins ( /products/jenkins-reviews ) for some tasks, which suggests there may be areas for improvement in GitHub Actions.
GitHub Actions lacks a feature for automating the build process for mobile applications. I currently rely on GitHub Actions for web applications but have to use another tool for mobile apps.
The main challenge I've experienced is with integration, particularly uploading to OneDrive, which was more complex compared to Google Drive or AWS S3 bucket. I had to conduct extensive research to find a solution using RClone for configuration. Focusing on making integrations smoother would be beneficial.
GitHub sometimes makes it difficult to debug actions. Improvements in debugging could enhance its usability greatly.
There could be more integration options with different platforms.
In terms of improvements, I think better logging for debugging purposes would be helpful, especially for complex workflows.
The primary area for improvement I see is in artifact management, especially for saving screenshots or videos from failed tests or data-driven actions. Currently, the configuration for saving these artifacts is complex. Simplifying this process would make GitHub Actions even more user-friendly and efficient. Other than this aspect, GitHub Actions stands out as an excellent tool for automating and managing workflows. For additional functionalities, one aspect I'd like to see improved is the integration of performance testing and API automation projects directly within GitHub Actions, without the need for third-party tools. This direct integration would streamline the process significantly.
There is a part that detects outdated libraries. If that feature could be more intuitive and informative, that would be nice.
I feel that the product is okay for me. Sometimes, it takes a while to deploy the product. Some of the functions of the product are hard to understand owing to its scripts or UI. The solution's integration capabilities and UI are areas of concern where improvement is required to make the product more user-friendly.
While our current pipeline handles most of the deployment, we believe there's room for improvement, especially when it comes to generating comprehensive reports and metrics. The reporting capabilities are somewhat limited.
We can leverage this database tool to manage everything within our environment and data burners, allowing for customization and execution. An additional advantage is the capability to modify aspects like file size, making processes more efficient and faster across the pipelines. Regarding improvements or implementations, I believe there should be enhancements made to the deployment tool. It should be integrated as part of the solution. Infrastructure-wise, we already have tools like GitHub and RobSpot, and data enables us to automate various processes, which is quite beneficial. As for further enhancements, I'm uncertain. I've shared everything I know. However, if there's something specific you'd like to see in future releases, a feature that may not exist yet but would be desirable, I can't provide any input on that matter.