Update sample_release_notes.md with complete release notes template #1
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.
Overview
Updated the
sample_release_notes.mdfile to provide a complete, properly formatted example for release notes in the Beacon project.Changes Made
Added Header Section
Improved Visual Spacing
Completed Build Artifacts Section
Previously, the Build Artifacts section was incomplete, showing only:
Now includes:
<app_name>and<mode>variablesfile_generatorin debug mode:bin/file_generator/debug/udp_replayerin release mode:bin/udp_replayer/release/Added Version Checkout Instructions
Added a new section "Checking Out a Specific Version" with:
git checkout tags/v1.2.3.4git checkout mainResult
The file now serves as a comprehensive example for developers creating release notes, providing all necessary information in a well-structured, easy-to-read format.
File Location:
scripts/pipeline/release/sample_release_notes.mdOriginal prompt
implement this.
nd added support for app-specific builds.
Bug Fixes
Improvements
Version History
Checking Out a Specific Version
To check out a specific version of the Beacon project, use the following Git command:
This will give you a read-only view of the source code for that version. To return to the main branch, run:
Changes Made:
###) between Improvements and Version History for clear separation.Let me know if this achieves the desired separation or if you’d like further refinements!
User: Can I see hte markdown
AI: It seems you're asking to see the Markdown content of the
AI: file. However, the file content is not fully visible in the provided context. Could you clarify if you'd like me to generate a new
AI: based on our discussions, or if you'd like me to assist with specific sections of the file? Let me know how I can help!
User: There is simply not enough space between Information / Versions. I'm talking Information: /n/n/n/n/n/n/n Versions.
AI: Here’s the updated Markdown for the Release Notes with significant spacing (7 blank lines) added between Improvements and Version History to ensure they are visually distinct:
This will give you a read-only view of the source code for that version. To return to the main branch, run: