|
From today you can now use Amazon Q Developer in Github in Preview! This is a fantastic news for millions of developers who use Github daily, where at work or for personal projects. Now they can use Amazon Q development for function development, control code and Java code migration directly without GitHub without the interface.
To demonstrate, I go to use the Amazon Q Development to help me create an application from zero called Storybook Teller. I want it to be ASP.CORE using .NET 9, which takes three images from the user and uses Amazon Bedrock with Claude Anthropic to create a story based on them.
I’ll show you how it works.
Device
The first thing you need to do is install the Amazon Q Developer in Github and you can start using it immensely without connecting to AWS accounts.
You will then be presented to add it to all your reather or choose a specific. In this case I want to add it to my report by demo fairy tale so I choose Only selected report and enter the name and find it.
That’s all you have to do to make Amazon Q Developer ready to use a selected rest. You can verify that the application is installed by navigation to your GITHUB account Settings and the application should be listed in Application page.
You can choose Configure You want to see permissions and add the development of Amazon Q to or remove it at any time.
Now we use Amazon Q Developer to help us create our application.
Development of functions
When Amazon Q developer is installed in renewal, you can assign Github from Amazon Q development agent to develop functions for you. It then generates the code using the entire code base in your rest as a context and a description of the problem. That is why it is important to list your requirements as accurately and clearer in your Github, in the same way you should always strive.
I have created five of the problems in my fairy -tale book that covers all my requirements for this application, from creating a project Skeleton .NET 9 to FRONEND and BACKEND Implementation.
Let’s use Amazon Q Developer to develop an application from scratch and help us implement all these features!
First I want Amazon Q Development to help create a .NET project. I will open the first edition and in Labels Section, I find and select Amazon Q Development Agent.
That’s all that is to do it! Amazon Q Developer is now assigned. After adding the label, the development of Amazon Q will automatically work behind the scenes providing progress updates through comments, starting with one proverb, I'm working on it.
As you could expect, the ament of time that takes will depend on the complexity of the function. When it is done, it automatically creates a request on request with all changes.
Another thing I want to do is make sure the generated code works, so I download the code changes and start the application locally on my computer.
I go to my terminal and type git fetch origin pull/6/head:pr-6 You want to get a code for request for request that he created. I will check the content and see that I really have the project asp.Core generated using .NET 9, as I expected.
Then I run dotnet run and open the application using the URL listed in the output.
Great, it works! Amazon Q Developer took care of the implementation of this one, as I wanted, based on the requirements I provided in the problem of Github. Now that I have tested that the application works, I want to check the code itself before I come.
Check the code
I will go back to Github and open the request for a move. IMUSEYTELY Thed that Amazon Q Developer performed some automatic inspections of the generated code.
That’s great! It has done quite a lot of work for me. However, I want to check it before I column for request. To do this, I will go to Changed lines Tab.
I’ll check the code and I like what I see! Looking at .gitignore content, however, notice something I want to change. I see that Amazon Q developer has made good assumptions and added rules for exclusion for Visual Studio (VS) code files. However, the Jetbrains rider is my favorite integrated development environment (IDE) for .NET development, so I want to add rules for it.
You can ask Amazon Q Developer to explore and change using a normal code control flow in the GitHub interface. In this case, I add how to the code .gitignore says that add patterns to ignore Rider IDE files. Then I choose Start a reviewWhich causes a change in the review.
I will select Complete your review and Changes in request.
Soon after sending a review, I am redirected to the conversation card. Amazon Q Developer begins to work on it, continues in the same feedback and encourages me to continue the control process until I am satisfied.
Each time the developer Q makes the changes, it starts automated inspections of the generated code. In this case, the code sowhat was straightforward, so the automatic code was expected to not increase. But what happens when we have a more complex code?
Let’s take another example and use the Amazon Q Developer to implement a function to enable images on the web. I use the same flow I have described in the previous section. However, I have noticed that automated request checks this time indicated a warning and stated that the API generated to support image recording on the backend is missing control of authorization efficiently allowing direct public access. It explains in detail the security risk and provides useful links.
Automatically generates code design.
When it’s done, you can view the code and decide to commit changes if you are satisfied with the changes.
After repairing and testing, I am satisfied with the code for this problem and move after applying the same process to another. I assign to each of my remaining problems Agent Q for development, wait until it generates the code, and goes through the iterative review process and asks to solve any problems on my way. At the end of this software cycle, I will test my application and I am very pleased that Amazon Q Development has managed to handle everything from the project settings to the boiler code, to the more complicated backage and queues. Real developer with full stack!
I noticed some things I wanted to change on the way. For example, the default use of the API Invoke API to send recorded images to Amazon Bedrock Instatead of Converse API. However, because I did not state it in my requirements, it had no way to know. This emphasizes that it is important to be as accurate as possible in the names and descriptions of your problem, so that the Q Developer will provide the necessary context and be the most effective process of development.
After I said it, it is still a squareboward to check the generated code on request requests, add comments and let Amazon Q developers continue working on changes until you are satisfied with the final result. Alternatively, you can accept changes in the sweater request and create separate, that you can assign developers Q when you are ready to develop them.
Transformation code
You can also transform Legacy Java Codesses into modern versions with Q Developer. Currently, applications from Java 8 or Java 11 can be updated to Java 17, with other options in future editions.
The process is very similar to the one I have shown in this post earlier, with the exception of several things.
First, you have to create a problem at rest Github containing Java 8 or Java 11. In this case, it depends on the name and description of Goverly. It can even be a short name, such as “migration”, leave the description empty. Then we Tags, You assign Amazon Q Transform Agent Label to the output.
As before, the Amazon Q Developer will start behind the scenes before you generate the code on request to request that you can see. This time, however, it is Amazon Q Transform, which specializes in code migration and takes all the necessary steps to analyze and migrate code from Java 8 to Java 17.
Note that according to the documentation also requires the creation of a workflow. If you are not allowed to be enabled yet, there will be clear instructions to help you get EletHing set before attempting.
As expected, the amnt of the time required to perform migration depends on the size and complexity of your application.
Conclusion
The use of Amazon Q Developer in Github is like having developers with a full stack that you can work with in the development of new features, speed up the code control process and rely on increasing the position and quality of code. You can also use it to automate migration from Java 8 and 11 for Java 17, which makes it easier to start with this migration project that you could postpone for a while. The best of all is that you can do it all from the comfort of your own Github environment.
Now available
Now you can start using Amazon Q Developer today in Github, no AWS birth settings are required.
Amazon Q Developer in Github is currently in preview.
– Matheus Guimaraes | Codingmatheus
How’s the Blog of news? Take this 1 minute survey!
(This survey is hosted by an external company. AWS processes your information as described in the AWS Privacy Notice. AWS will own data collected via this survey and will not share information with dew survey.)