file and directory naming conventions #453
Merged
Conversation
This file contains 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
ultrasaurus
requested review from
dshaw,
JustinCappos,
lumjjb,
pragashj and
TheFoxAtWork
as code owners
TheFoxAtWork
approved these changes
Nov 12, 2020
Michael-Susu12138
pushed a commit
to Michael-Susu12138/tag-security
that referenced
this pull request
Dec 12, 2023
file and directory naming conventions
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I thought we had these written down, but couldn't find them when commenting on #452
Attempted to capture what is common practice across the repo -- we're not 100% consistent, but close