Skip to content

Fix incorrect bodyFile path in release.yaml#134

Merged
Malcolmnixon merged 2 commits intomainfrom
copilot/fix-docs-path-in-release-yaml
Mar 27, 2026
Merged

Fix incorrect bodyFile path in release.yaml#134
Malcolmnixon merged 2 commits intomainfrom
copilot/fix-docs-path-in-release-yaml

Conversation

Copy link
Copy Markdown
Contributor

Copilot AI commented Mar 27, 2026

Pull Request

Description

The bodyFile path in release.yaml included a spurious docs/ subdirectory prefix. The documents artifact is published flat (no folder structure), so build_notes.md lives directly under artifacts/, not artifacts/docs/.

  • .github/workflows/release.yaml: artifacts/docs/build_notes.mdartifacts/build_notes.md

Type of Change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update
  • Code quality improvement

Related Issues

Pre-Submission Checklist

Before submitting this pull request, ensure you have completed the following:

Build and Test

  • Code builds successfully: dotnet build --configuration Release
  • All unit tests pass: dotnet test --configuration Release
  • Self-validation tests pass:
    dotnet run --project src/DemaConsulting.ReqStream --configuration Release --framework net10.0
    --no-build -- --validate
  • Code produces zero warnings

Code Quality

  • Code formatting is correct: dotnet format --verify-no-changes
  • New code has appropriate XML documentation comments
  • Static analyzer warnings have been addressed

Quality Checks

Please run the following checks before submitting:

  • Spell checker passes: cspell "**/*.{md,cs}"
  • Markdown linter passes: markdownlint "**/*.md"
  • YAML linter passes: yamllint .

Testing

  • Added unit tests for new functionality
  • Updated existing tests if behavior changed
  • All tests follow the AAA (Arrange, Act, Assert) pattern
  • Test coverage is maintained or improved

Documentation

  • Updated README.md (if applicable)
  • Updated ARCHITECTURE.md (if applicable)
  • Added code examples for new features (if applicable)
  • Updated requirements.yaml (if applicable)

Additional Notes

Single-line workflow fix; no build or test changes required.


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

Agent-Logs-Url: https://github.com/demaconsulting/ReqStream/sessions/d8e5cbfd-8feb-47eb-b111-9e9b7d155d46

Co-authored-by: Malcolmnixon <1863707+Malcolmnixon@users.noreply.github.com>
Copilot AI changed the title [WIP] Fix incorrect docs path in release.yaml for build_notes.md Fix incorrect bodyFile path in release.yaml Mar 27, 2026
Copilot AI requested a review from Malcolmnixon March 27, 2026 14:56
@Malcolmnixon Malcolmnixon marked this pull request as ready for review March 27, 2026 14:58
Copilot AI review requested due to automatic review settings March 27, 2026 14:58
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Fixes the GitHub Release workflow to reference the correct location of the generated build notes file when creating a release.

Changes:

  • Update bodyFile in the release workflow from artifacts/docs/build_notes.md to artifacts/build_notes.md to match how the documents artifact is downloaded/unpacked.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@Malcolmnixon Malcolmnixon merged commit 5d53fee into main Mar 27, 2026
19 checks passed
@Malcolmnixon Malcolmnixon deleted the copilot/fix-docs-path-in-release-yaml branch March 27, 2026 15:06
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.

3 participants