Add docs for HTTP.Sys CBT hardening#37086
Conversation
wadepickett
left a comment
wadepickett
left a comment
There was a problem hiding this comment.
Approved. This is super clean, I"m not finding anything to address!
|
Do we put any metadata when content is created with help from AI? |
| @@ -1,3 +1,3 @@ | |||
| --- | |||
| title: HTTP.sys web server implementation in ASP.NET Core | |||
| ai-usage: ai-assisted | |||
There was a problem hiding this comment.
ai-usage: ai-assisted already in the doc, so no need to add it here.
Added ai-usage: ai-assisted metadata
Done, thanks for the heads up. |
|
Just a side note on AI tools for this repo since AI was mentioned (OK, a bit out of scope, but I'll drop this in anyway): I set up some GitHub Copilot agent, skills, and instruction files on this repo early in the year to help Copilot out when it's assigned an issue. It can handle more as a result, but still requires close scrutiny — and in many cases some of the work is just moved to the review, where it's corrected or reorganized manually as needed. I also set up a triage instruction set that generates a report and action plan that can be dropped into the issue discussion, so we can get a sense of how Copilot would handle it, make changes, and then assign it to Copilot if we think it's a good fit. On the issue, select Copilot so the issue is in context, then use the following prompt (non-blazor for this one): For this GitHub Issue as context, follow all instructions here: Review, adjust the action plan in report if needed, and drop it in the discussion. Copilot will pick it up when assigned to the issue, it knows to look for it on this repo. Next, I will get it more integrated as a default agent that runs in the issue creation workflow. |
|
@BrennanConroy, I thought I would hold off merging to give a chance for other reviews to come in, but it has been a few days. Should I go ahead and merge? |
|
Yeah, feel free to merge |
2 participants
Internal previews