Fix/set valid tag#2
Conversation
Updated guidelines on uninitialized memory usage and added examples of compliant and non-compliant code.
Added noncompliant and compliant examples demonstrating safe /unsafe memory initialization in Rust.
There was a problem hiding this comment.
Pull request overview
This PR fixes invalid tag usage and resolves a duplicate ID in the coding guidelines documentation. The changes ensure the build succeeds by replacing the non-existent "unsafe" tag with valid "safety" and "security" tags, and by generating a unique ID for a compliant example that was previously duplicated.
- Replaced invalid "unsafe" tag with valid "safety" and "security" tags
- Changed duplicate compliant_example ID to a unique identifier
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
Was this attempting to add tags as @rcseacord did on this PR? Note that it's necessary to add the tag to |
I found I misunderstood your intention. I'll make a new PR. |
57f303a to
4b8cbc7
Compare
9b81ff4 to
0e2776c
Compare
|
I solved this issue in another PR so I'm closing this. |
Patch for this PR.
The build was successful in my local environment.