GitHub CoPilot Reviews

I am maintaining my code as a code repository and using my student account with GitHub CoPilot.

GitHub CoPilot is easy to use even for beginners and it supports the integration with CI/CD tools. It is helping organizations by creating frameworks. CoPilot is a main selling point.

GitHub CoPilot is easy to use and is integrated with CI/CD tools. It is helpful for creating frameworks and saves most of my time, around 70%. CoPilot is the main selling point.

They could simplify the API integrations and allow us to automate certain tasks using our own server without just logging into the web page. They can also improve the scope of CoPilot.

I have been using it for the past one and a half years.

I haven't faced any downtime or critical issues in my experience.

I don't feel any restrictions regarding scalability, even large organizations are using it. However, I can't comment much on scalability as I am using a personal account.

Technical support for GitHub is available.

I am using GitLab, but GitHub has more add-on features and subscriptions. GitLab is kind of limited and lacks add-ons like CoPilot.

The setup is easy and straightforward. One can complete it in about thirty minutes.

I helped some of my team members configure CoPilot on their systems.

For organizations, the return on investment is good mainly due to CoPilot. But for personal paid accounts, it feels quite pricey.

For personal accounts, it seems pricey. However, for organizations, it is a good value for money.

I have also used GitLab.

CoPilot is supporting and they can improve the scope. They should allow for more involvement from beginners to explore features within the GitHub environment.

I'd rate the solution eight out of ten.

If I want to find things quickly and easily, I'll use it for content, but I don't cut and paste. It's like I'm checking my ideas.

If you had a Microsoft Teams environment, we could use it to create a virtual agent or something. I know the general things I can do with AI and chat engines.

I use it almost like a search engine, but it goes a step beyond. A search engine shows you many results, and you have to read everything to put it together. But with CoPilot, you ask a question, and it gives you a summary of all the websites out there. So it's faster learning.

It handle complex tasks as well. It is able to generate results that I want. 

The problem arises when a bot is not well-designed, which frustrates customers.

For example, with our local Comcast cable company, if you need to repair something, you go on the app. They ask, "What's wrong?" You say, "My power cord melted. I need a new power cord." But the bot responds, "Oh, your Internet's not working?" 

So, it doesn't recognize unusual issues. Then, they make you go through troubleshooting, saying, "Your Internet looks good, but your device isn't plugged in." It's like, "Yes, I know. I want to speak to an agent." 

And it takes another ten minutes of trying different things before you finally get to an agent.

This is an example of a poorly designed bot.

I have been using this solution for about a year.

It's the self-service type. We just use it very simply.

We just use it for the same reasons I do. We do work with other providers and program virtual agents or bots. Those are all the rage now. You put them on your website. You used to have simple ones like "I can check your deposits or cancel a check for you," but they're limited to what you program. 

But if you expand a bot like Swifter Robot with artificial intelligence and natural language processing, then it can almost be like a person. Then, you can do some really cool things with it. 

I haven't encountered any issues. When I do, I just call our IT group. I haven't had any problems with it, unlike OneDrive.

I believe it's just standard with Microsoft, so you download it with their installer.

Increased productivity and improved customer experience can count as an ROI. If customers need to know something, they'll either wait five minutes for an agent or they can just go ahead and find the answer themselves. Most will choose the latter. The problem is poorly designed bots that frustrate customers. 

We have a team that decides on the best tools, like Google Digital or other products.

I would recommend it because it's part of the Microsoft package, it's easy to use, and I haven't found any of the answers to be outrageous.

Overall, I would rate it a seven out of ten because I haven't used it enough.

I primarily use GitHub Copilot for coding and also utilize natural language prompts to get some code suggestions. 

Additionally, I use it after the development team completes their work to check for any vulnerabilities, as it provides a vulnerability report.

In terms of functionality, the code suggestions in GitHub Copilot are particularly helpful for project development. It provides valuable insights into errors during compilation, allowing me to ask within Copilot itself for solutions without needing to search the internet or use platforms like Stack Overflow. This capability makes problem-solving more efficient.

In terms of understanding user queries and providing code that aligns with my expectations, there is room for improvement. Sometimes it requires multiple iterations to get the code I need, like for creating a login page with specific buttons and logic. 

A UI feature for drag-and-drop functionality, along the lines of services provided by Bubble or Wix, integrated with coding prompts, would be more beneficial. This would streamline creating code snippets for common tasks, increasing user satisfaction.

I have been using GitHub Copilot for more than six to eight months.

I would rate the stability of Copilot at eight or nine out of ten. Initially, there were some setup problems, but after that, it has been stable.

GitHub Copilot's support could improve by having a community and more detailed onboarding to encourage users to adopt the solution.

Neutral

I frequently use OpenAI's paid version, which offers excellent features, such as analyzing entire zip folders and providing insights. This helps with tasks like comparing different developers' outputs based on high-level requirements, which meet my expectations well.

The initial setup was straightforward. It required activating my account and connecting it, after which everything was seamless. A restart of the IDE ensured the model detection was resolved.

The pricing for GitHub Copilot is around $10 per month. While it offers significant productivity gains, lowering the price to $5 could encourage more users. If the price were lower, it might be more worth it, even if only used a few days a month.

I compared GitHub Copilot to OpenAI, which provides great features like analyzing zip folders and ranking inputs, meeting my requirements better.

On a scale of one to ten, I rate GitHub Copilot around seven to eight. GitHub should offer more competitive pricing and could benefit from incorporating functionalities like providing code analysis for entire zip folders to improve user experience.

I use the platform to assist with code suggestions and improve the efficiency of our software development teams. It helps with code assistance for novice programmers by providing them with coding best practices. 

The platform's most valuable feature is its code suggestion capability, which leverages AI to provide context-aware suggestions. It improves the coding skills of less experienced developers and speeds up the development process by reducing the time spent debugging and rewriting code.

They could improve the product in terms of integration with other tools.  Additionally, they should offer more robust support for highly regulated environments like finance or healthcare to enhance its applicability.

I have been using GitHub Copilot for a significant period. 

The solution is stable.

The product is highly scalable, as adding more licenses can be done easily without additional infrastructure costs.

The support team is knowledgeable and responsive.

Previously, I used Appian BPM, but the focus has shifted towards more modern technologies like DevOps and AI in DevOps. We switched to GitHub Copilot for its advanced AI-driven code assistance and seamless integration into the cloud-based development environment.

The initial setup was straightforward, involving license acquisition and basic configuration.

We implemented the product in-house. 

The return on investment is substantial, with an estimated ROI of 500%.

The product has a tiered pricing model that starts with a free version for individual developers but requires a separate license fee for enterprise use.

I rate GitHub CoPilot an eight out of ten. 

Most of the time, it is for code suggestions. It allows improving the efficiency and productivity of development. It is used by developers within the IDE, so the development environment.

Not that much, as I need to wait until the ongoing pilot ends to have final feedback. However, it is expected to improve coding productivity and the capacity to produce quickly and more efficiently.

The most known and important features from a development point of view are the code suggestions. It enhances efficiency and productivity in development. 

The merge request features and workflow are available. We don't use them much currently. GitHub Copilot enables the production of business projects quickly and efficiently.

I cannot really answer this one as I don't have enough experience to share this kind of feedback. Someone who uses it daily might better understand these questions.

I have used it for around six months.

Very high stability. I didn't notice any issues regarding stability.

The AI model is really scalable, so I would rate it at least nine out of ten. I am optimistic about the next releases being developed and designed.

I do not have experience contacting technical support, so I cannot provide feedback on this aspect.

Positive

Before GitHub Copilot, we evaluated GitLab with its Duo feature. Developers chose Copilot because of stronger code suggestions.

The initial setup was easy, particularly within the IDE. Minimal complexity was involved.

We use GitHub Copilot internally with the client's company. It is an internal project, and as an architect, I was involved in the discussions to decide between Copilot and other solutions.

I need to wait until the pilot we are undergoing ends to get a clear understanding of the ROI and productivity improvements.

I am not really included in the cost management part, so I don't have insights into the pricing or setup costs.

The other option considered was GitLab Duo. Based on presentations and evaluations, we chose GitHub Copilot due to its stronger code suggestion capabilities.

I would initially rate it nine out of ten based on what I know and the small experience I have had. For it to be ten out of ten, it needs more advancements in the AI part, though it is already strong. Future updates are anticipated.

I'd rate the solution nine out of ten.

Today, if you're aware of the CI/CD requirements, then it's fine. Unless you know how to create the pipeline, it would be tough. The one I'm using is already set. So I can implement it immediately. If there is a deviation from that, then it will be a little tough, I would need to Google to find the solution. I can implement it.

When you're using it, it's automatically deployed. In a normal application, it used to provide a single application. In this proprietary thing, it is just now it used to provide in the scripting tag, you need to provide Spring Boot.run, and that server code. So that unit is forwarded. In Copilot, you need to mention which nodes you are going to configure. So you need to provide all the port numbers and then deploy there. It will automatically deploy everywhere.

The deployment is easier when you're handling multiple deployments. So, I don't need to node application unit for node, update, and everything everywhere. But it's also in the engine we can do there. 

Once you set up everything, it is automatically handled. But once the setup is done, it's done.

GitHub Copilot code suggestion capabilities: It's always good. When you're doing any deployment, the suggestions are always welcome. You don't need to remember everything. You can pick from the solutions provided.

One thing I noticed is that normally, in CI/CD pipelines, we put: 

• the Jenkins path, 
• the Git repository paths, and 
• the number of reports we are going to deploy.

If we had an automatic system, an automatic page to do all these things, it would be easier. Not a configuration, but a page. If you have that kind of page, then Copilot can help all the developers. This is my individual preference. It can be there, it may not be. Maybe I'm not able to explore those issues, but that is one thing I noticed.

Currently, we need to map everything. We need to provide the Git card and where we need to deploy. If it is pre-prod, stage, or production, we need to map it separately. If we had some kind of program and could take it from the application of properties file, it would have been great. We configure everything in separate files. 

Even for development, staging, and production environments, we need to make separate files for each. If you have some mechanics to automate that, it would be great. It's for the entire system. Their system is like that. You need to prepare separately for every manage. So if you have one utility to make all those alternates, it would have been great. A UI would enhance the developer experience and streamline the CI/CD process.

You need to configure it separately for each environment. If everything is in a dropdown, it could be directly included. It will automatically connect to your dedicated agent. But it is okay. As of now, it's working fine. It's just manually maintaining that data. It worked fine. No issues. That is the only suggestion I have.

TL;DR:

For different environments, like production, stage, and development, if we can have a single point, like one, two, or three instead of opening for each, that feature would be helpful. We have numbers for certain regions, but again, the developer and the team should remember which number is for dev, stage, and prod. That could be easier for maintenance. 

The administrator doing the CI/CD pipeline should remember that number. It can be easier for any AI tool to do that. Instead of putting the phase in the configuration, if you put in a AI tool, it is easier for the system to manage.

I have been using it for three months. 

It's stable. 

It's scalable.

In the last team that we had around 13 members, everyone never faced any issues when using Git merge and Git commit. You have a separate Git repository, and you just need to know how to use it. The only thing is, our case of sessions should be organized, and the resources should be proper.

You want to see what everything the account does. I do everything with a command prompt, not using any Git GUI. You'll get the GUI application for your commit and such. It's fine.  

Deployment time: If the database scripting and the data center information are ready, then it will take one or two hours. It's a server configuration. Two to three hours of work.

Deployment resources: I can also do it. It doesn't require multiple people. If the software is ready and everything is fine, then only one person can do everything. That is what a full-stack developer means. If you are a full-stack developer, it means you can handle all the data-related tasks and services. I'm a full-stack developer, so I'm ready to do that. I should have the capability to do everything on the website.

We have a separate team to do that. They will do the things for us. From my side, I just raise a ticket in Jira support, and then they will take the ticket and implement it. The installation and configuration is a separate process because in each organization, they have separate monitoring systems.  

There's a separate team to make those things happen for me.

Overall, I would rate the solution a nine out of ten. The only suggestion is to enhance Copilot's ability to assist developers with infrastructure as code tasks.

Like, while using CI/CD pipeline, when I use YAML files, so it could just support the port number. That will improve the feature. But the developer should be aware of the feature.

We use the platform to accelerate coding by providing relevant code suggestions and automating repetitive tasks. I use it in a development environment focused on various programming languages, where it helps by predicting code snippets and detecting variable names, which speeds up the coding process.

The platform's most valuable feature is detecting and suggesting variables based on the existing file context. This feature streamlines coding by offering relevant variables, making it easier and faster to write accurate code.

They could enhance the product's accuracy of suggestions, especially when dealing with non-standard or legacy code. Additionally, an easier and more intuitive way to toggle Copilot on and off would be beneficial.

I have been using GitHub Copilot for a few months.

The code prediction is generally stable, though there are occasional inaccuracies. 

The initial setup was very straightforward. 

The implementation was done in-house.

The return on investment may vary depending on the project. The predictions aren't always accurate for large enterprise solutions or extensive codebases. However, for standardized projects, it can significantly improve productivity.

GitHub Copilot is a paid service, costing approximately $6 per month. There might be a free trial available.

I decided to try GitHub Copilot because of its integration with GitHub and my existing workflow.

GitHub CoPilot is quite capable of AI. It provides good suggestions and aids in coding, but the increase in productivity is modest.

I recommend that others analyze if it works for their requirements. It's important to assess if it fits their workflow before fully integrating it into their coding practices.

I rate it a seven out of ten.

I just installed the product idea in my ID extensions, as it will be handy for auto-completions and suggestions. Sometimes, I use the tool to simplify the code and for documenting the code.

I like how GitHub CoPilot analyzes individual docstrings and keeps the method context relevant. Instead of throwing random codes, GitHub CoPilot sticks to a class of more context-relevant code generation, which I like.

Speaking about the code suggestion capabilities of the product, I would say that though it is good, there is a need to develop it further. In our company, when we have more dependent classes opened, we realize that GitHub CoPilot needs to be improved. GitHub CoPilot needs to analyze the whole package and try to give more relevant codes.

If the product plans to provide more extensions, then adding Eclipse would be helpful. There are no extensions provided by the product for Eclipse.

I wish the context window gets expanded, as it would be good for the product, especially since I am currently using some custom packages and custom classes. GitHub CoPilot needs to give some generic code generation instead of analyzing my classes and giving relevant codes. Apart from the aforementioned area, there are no major challenges in the tool.

I have been using GitHub CoPilot for ten months. I am a customer of the tool.

There are no stability issues with the product.

I don't know how to comment about the scalability feature of the product since it is just used as an extension.

I have not worked with other solutions, and I believe that GitHub CoPilot has a monopoly in the market because there is no other free tier version of other products in the market variable that meets my expectations.

The product's initial setup phase is easy.

The solution can be deployed in five minutes if you have activated a GitHub CoPilot account.

I have definitely experienced an ROI from using the product. It saved my company 30 percent on costs and time.

The pricing is reasonable. I think it is 10 USD per user.

The AI integration in the product is good.

If you are new to coding and you want to save some time by not writing a course from scratch, then you can definitely use GitHub CoPilot, as it saves a lot of time in the initial stages of development but not in the more advanced production-ready stages.

I rate the tool an eight out of ten.

Whenever I need to write test cases for my development code, I just give the command to Copilot, and it automatically helps me write them. Then I just need to review them. It also really helps me write the skeleton of the basic design. It won't give me a 100% solution, but it gives me a 75% solution. Then I just need to review it, make some cosmetic changes, and it's ready. 

Overall, where I used to spend a whole day on test-related activities, now I just need to spend two to three hours, and I can complete my job.

It's helped reduce engineering effort. If I can complete my job in half a day, then all the engineers can complete their jobs in half a day. Ultimately, it saves cost and optimizes performance. 

From the company perspective, if we needed to spend a million dollars, we can now reduce it to at least a hundred thousand dollars.

Copilot's code review, test case generation, and chat features are most valuable to me. When I write code, I feel like I have someone sitting with me to help me. Wherever I'm stuck, I just ask a question, and it provides guidance that I can use.

In a few cases, the results aren't correct, so that needs improvement. Also, it would be great if the results could be presented in different formats, not just text. As engineers, it takes time to read through text-based results. 

If they could provide diagrams or basic design architectures, it would be easier to understand and take less time to review. So, as of now, image functionality is not provided by GitHub Copilot, and it would be great if they could add that.

So, I would like to see improvements in the result generation, more results, different result formats, and image functionality.

I have been using this solution for four months. I work with the latest version.

I would rate the stability a nine out of ten. It is a stable product. Copilot is a good thing when you're writing code. It assists you wherever you need it. 

On the other hand, there are a lot of benefits to this feature, like suggesting code before you write it and suggesting the optimal way to write it, which is really helpful. 

Apart from that, it helps with writing test cases and suggestions for heavy algorithms where you need to put in a lot of brainpower. So, it makes things easier.

On the other hand, the negative points, Copilot still hasn't reached a point where we can trust it 100%. Sometimes, when we raise a query, it stops working intermittently. So, at that moment, we need to look for other options. It's not, as of now, 100% reliable. Sometimes, it stops working; sometimes, the output has issues. So, we need to be careful with information.

I would rate the scalability an eight out of ten. Sometimes, we face high traffic on Copilot, and it stops responding to our queries. It's happened a few times, maybe three or four times out of a hundred.

It's not 100% reliable. Sometimes, we stop receiving responses. We have around 500 end users in our company. It is used on a daily basis. 

The customer service and support are okay. 

Positive

We switched to GitHub because it's more appropriate and saves me time. On Google, I need to spend time searching for something, typing it in, and then getting a bunch of solutions out of which I need to pick the best one. 

Copilot, on the other hand, gives me the best answer out of all the possibilities with just one query. That's a big benefit.

I would rate my experience with the initial setup of this product a seven out of ten, where one is difficult, and ten is easy to set up. 

It is not complex. I gave it a seven because there were a few minor technical challenges with the initial login. It wasn't as smooth as logging in to Gmail or Microsoft Outlook, but I was able to log in after a few tries. 

So, it is a bit tricky. These are just minor challenges, not completely smooth. 

We use the licensed version, not a cloud version. We purchased a license and installed it.

We did everything ourselves. I was able to do it alone; it didn't require much effort. So, one person can manage both the deployment and maintenance.

It took only one day to deploy it. It's not really a deployment in the traditional sense. We requested a license key from Microsoft, and then we used that key to log in from our laptops. We configure it with our development environment, and it works smoothly.

If you invest some amount, it will definitely reduce your production cost. I would rate the ROI an eight out of ten, where one is low ROI and ten is high ROI. 

I would rate the pricing a five out of ten, where one is very cheap and ten is very expensive. So it's affordable.

There are no additional costs to the standard license. So the price is fixed.

This is the first time I've used a tool like this that assists with code writing. Before that, I used a simple Google search. 

Moreover, Google has recently launched its feature, but it's not as mature as Copilot's. They're in the very early phase.

Developers, testers, front-end, back-end, any developer can use it. It's really beneficial for them. On the other hand, testers can also explore test cases with Copilot. It'll help them, too.

Overall, I would rate the solution an eight out of ten. 

GitHub CoPilot can be used for prompt engineering, delivering information to create a presentation, and comparing results from other AI tools, like ChatGPT or Gemini. You can use the CoPilot app while creating presentations, but we need to subscribe and pay an additional fee to use it. I'm truly considering talking to the management team to contact Microsoft to see if we can use that feature. It's a very useful feature.

The CoPilot app that you can use while creating presentations is very useful.

It would be useful if we could use the solution to create documents, not only prompts. It would also help if we could insert documents and create results in accordance with the documents inserted.

The tool has a feature that allows you to upload a voice document or a recording, and it can export the transcription for that recording. This transcription is not available in all languages. I would like to know whether the solution plans to expand the number of languages because I want to know if there's also a plan for Hebrew transcription.

There are limitations because you have to subscribe and pay more money to use the GitHub CoPilot tool.

I have been using GitHub CoPilot for a few months.

I rate the solution an eight out of ten for stability.

I rate the solution’s scalability an eight out of ten.

I've tried to contact Microsoft, but I haven't received a response. I'm not impressed with the technical support.

The solution's initial setup is pretty straightforward, but I'm not as impressed as ChatGPT and Gemini.

With GitHub CoPilot, we have more opportunities and can approach more people in less time. The solution shortens the time it takes to finish a certain task.

We have a license but need another one for the GitHub CoPilot tool.

Overall, I rate GitHub CoPilot an eight out of ten.