Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

App Service GitHub Copilot for VS Code #495

Merged
merged 3 commits into from
Jan 28, 2025
Merged

App Service GitHub Copilot for VS Code #495

merged 3 commits into from
Jan 28, 2025

Conversation

seligj95
Copy link
Collaborator

Summary

Copy link

Preview link: https://antares-blog-staging-pr-495.azurewebsites.net

  • Your changes have been deployed to the preview site. The preview site will update as you add more commits to this branch.
  • The preview site shows any future-dated articles. If you are publishing a future-dated article, it will not show on the production site until the file's specified date.
  • The preview link is shareable, but will be deleted when this pull request is merged or closed.

This is an automated message.

@seligj95 seligj95 requested a review from madsd January 27, 2025 20:05

Before we get started, I want to give a shout-out to [GitHub Copilot](https://code.visualstudio.com/docs/copilot/overview), which if you're using VS code and your not using GitHub Copilot yet, you should definitely check it out. [GitHub Copilot](https://marketplace.visualstudio.com/items?itemName=GitHub.copilot) is your AI pair programmer tool in Visual Studio Code. Get code suggestions as you type or use Inline Chat in the editor to write code faster. Add new functionality or resolve bugs across your project with Copilot Edits, or use natural language in chat to explore your codebase. Also calling out that you can definitely do what we'll be doing in this blog post without GitHub Copilot and instead use a different Copilot implementation or other AI tool altogether, but using GitHub Copilot directly where you're writing your code and building your ARM/Bicep templates is a great way to make your process quicker and more efficient.

In this blog post, we'll be discussing how to implement best practices, when it comes your Azure App Service resource, into your Azure ARM/Bicep templates with GitHub Copilot. There's two entry points to this blog post. The first is that you're new to ARM/Bicep templates or App Service and you're looking to learn App Service best practices as you start writing your templates. The second is that you're already writing ARM/Bicep templates and you're looking to improve your templates by implementing best practices that the product group recommends. If either of these entry points apply to you, then this blog post is for you.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something wrong with the first sentence here.

Some follow-up questions you can ask GitHub Copilot include:

```md
1. Can you help me configure the App Service Plan with the recommended settings?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"md" bullets does not seem to work here.

1. Can you help me configure the App Service Plan with the recommended settings?
1. Can you help me configure the App Service with the recommended settings?
1. What properties should I set on the App Service to make it secure?
1. What other resources so I include in my template to make the App Service reliable and performant?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What other resources should I ...

@seligj95 seligj95 deployed to production January 28, 2025 16:34 — with GitHub Actions Active
@seligj95 seligj95 merged commit 63cbe72 into master Jan 28, 2025
4 checks passed
@seligj95 seligj95 deleted the ghcopilot branch January 28, 2025 16:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants