Update organization and repository references to Safety-Critical-Rust-Consortium#1218
Open
MarcosBorgesPhD wants to merge 3 commits into
Open
Conversation
Safety-Critical-Rust-Consortium
✅ Deploy Preview for scrc-coding-guidelines ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
1 participant
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.
While exploring the project to better understand our WIP and CI workflows, I noticed some references that aren’t updated.
This PR updates hardcoded repository URLs and documentation links across the codebase to point to the new location, replacing
rustfoundationwithSafety-Critical-Rust-Consortiumwhere necessary.Changes
README.mdwith the corrected link to the active work items board.REVIEWING.mdwith the updated link to consortium members.Safety-Critical-Rust-Consortium/safety-critical-rust-coding-guidelines).Reviewer Notes
I checked the GitHub API and intentionally left historical user fields (like
"user": { "login": "rustfoundation" }) untouched. This maintains identity integrity and prevents API404errors on those endpoints.