Delete style guide files no longer maintained in this repo#177
Merged
compiler-errors merged 2 commits intorust-lang:masterfrom Jun 22, 2023
Merged
Delete style guide files no longer maintained in this repo#177compiler-errors merged 2 commits intorust-lang:masterfrom
compiler-errors merged 2 commits intorust-lang:masterfrom
Conversation
Member
Author
|
I added f0aec1d as a separate commit to make it easier to revert in case anyone feels strongly that we should keep it. However, I think if we're going to utilize templates in this repo then we should consider doing so via a GitHub Issue Form or Template |
Closed
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
2 participants
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.
As agreed at the last t-style meeting we're removing these files because the style guide text has been moved to the main rust-lang/rust repo at https://github.com/rust-lang/rust/tree/master/src/doc/style-guide and we don't want these artifacts to become a source of confusion