GitHub

Having all our Java and Selenium scripts stored in such a well organized, dependable environment has really made my day to day work a lot smoother. I especially like how the pull requests make it straightforward for my teammates to look over any updates I make and spot issues before anything gets merged to main. The agent is not just there to help with writing lines of code anymore, it really feels like I have an extra set of hands in the process. I can ask it to update several page objects at once or create a whole new test suite for a fresh scenario and it takes care of everything, even if that involves changing multiple files. If I run into a test failure, I can tell agent to handle it right there in the terminal, and it'll keep trying out solutions on its own until things work. I no longer have to spend ages doing all those tedious set-up and maintenance tasks I used to dread. I've also noticed a big improvement when it comes to debugging. When a stubborn test keeps failing, agent often spots those sneaky little mistakes I might miss myself, like a single-character typo in a JSON path. Thanks to this, my testing cycle is a lot smoother and tackling complex scripts doesn't feel overwhelming anymore. Honestly, I'd find it difficult to go back to coding without this kind of help.

Supports other GitHub product: It supports other Git products very easily which is one plus point according to me Robust Security Measures: As someone who values security I am impressed by GitHub Enterprise's commitment to keeping our code secure Customization: There are very customization options which helped us to save some time as well as money

1. GitHub Actions. Specifically, being able to create CI/CD pipelines that live within our code. The flexibility of when and where those actions run helps us run the right scan or build at the right time without devs having to worry about forgetting to kick off a job. 2. Integrations. Beyond just the massive amount of integrations that other tools have with GitHub, the integrations within the platform itself are phenomenal. As a GHAS customer, this especially shines with GitHub CoPilot for Security tackling and creating issues that are discovered. 3. Scalability with Pull Requests. The ability to manage PRs, reviews, checks, and branch protection at scale makes it easy to enforce code quality and security gates across our enterprise without slowing our development teams down.

The things I dislike about this product are very minor and not a dealbreaker. Honestly, I struggle to find anything major to complain about because the tool is just so good for our automation work. If I had to pick something, it would probably be how the copilot agent can sometimes be a little bit too eager and gets exited to suggest changes. Occasionally it tries to refactor a piece of code that I want to keep exactly as it is and I have to go back and undo its suggestions which can be a tiny bit annoying. Another small thing is that, once in a while, the agent gets a bit confused with our very specific custom libraries in the framework. Since it is trained on so much public code it sometimes defaults to standard selenium ways of doing things instead of using the custom wrappers we have built in our java project. But again it is such a small issue compared to how much time it saves me every single day.

Initial Setup Complexity: the initial setup can be quite complex, for the non-technical, first-timer and for the fresher Cost Concern: The cost is a little bit high according to me if it can get a little bit cheaper then it will be a win-win situation Learning Curve: Learning takes time because it has a wide range of features which are a little bit complex for first-timers like me

1. Limited native environment modeling. When looking at other CI/CD tools, GitHub doesn't have as strong native concepts for environments, promotions, or release orchestration without building it out ourselves. The ability to do so is there, but it requires much more hands on work. 2. Actions and runners costs. This has been a hot topic recently, but self-hosted runners and action usage in general need active monitoring, or you will end up with a surprise bill. 3. Pipeline complexity. This isnt a unique problem to GitHub, but as pipelines grow, managing runner costs, permissions, and reusable workflows requires more structure than GitHub gives you out of the box.