Formalize build_notes.md path and artifact handling#75
Merged
Malcolmnixon merged 2 commits intomainfrom Mar 26, 2026
Merged
Conversation
…teDotNetLibrary PR #66) Agent-Logs-Url: https://github.com/demaconsulting/TemplateDotNetTool/sessions/f857d5ca-35b8-4bbb-b5ee-fe26dbb234b4 Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Merge pull request #66 from sister project
Formalize build_notes.md path and artifact handling
Mar 26, 2026
Contributor
There was a problem hiding this comment.
Pull request overview
Aligns the release workflow and agent documentation with the actual build_notes.md generation/output location, removing an unnecessary workaround step.
Changes:
- Update release workflow to use
artifacts/build_notes.mddirectly as the GitHub Release body file. - Correct the technical writer agent’s documentation tree and example link to reference
docs/build_notes.md(notdocs/build_notes/build_notes.md).
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| .github/workflows/release.yaml | Removes the move-to-root workaround and points bodyFile at the downloaded artifact path. |
| .github/agents/technical-writer.agent.md | Fixes the documented docs tree and example reference for build_notes.md. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pull Request
Description
Ports TemplateDotNetLibrary#66 to this repository.
build_notes.mdis generated atartifacts/build_notes.mdafter artifact download. The release workflow was unnecessarily moving it before use, and the agent documentation incorrectly placed it underdocs/build_notes/rather thandocs/.release.yaml: Remove "Move build_notes.md to root" step; useartifacts/build_notes.mddirectly asbodyFiletechnical-writer.agent.md: Fix structure diagram —build_notes.mdatdocs/level (notdocs/build_notes/build_notes.md); update example reference todocs/build_notes.mdType of Change
Related Issues
Pre-Submission Checklist
Before submitting this pull request, ensure you have completed the following:
Build and Test
dotnet build --configuration Releasedotnet test --configuration Releasedotnet run --project src/DemaConsulting.TemplateDotNetTool --configuration Release --framework net10.0--no-build -- --validateCode Quality
dotnet format --verify-no-changesQuality Checks
Please run the following checks before submitting:
./lint.sh(Unix/macOS) orcmd /c lint.bat/./lint.bat(Windows)Testing
Documentation
Additional Notes
No functional behavior change —
docs/build_notes.mdwas already the correct output path. This removes the workaround in the release job and corrects the agent documentation to match reality.🔒 GitHub Advanced Security automatically protects Copilot coding agent pull requests. You can protect all pull requests by enabling Advanced Security for your repositories. Learn more about Advanced Security.