Merge Branch Insider-Threat-Sonny into Main Branch #80
Conversation
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
added 30 commits
August 25, 2025 23:12
…erprises/CyberSafeVR.2 into Insider-Threat-Sonny
…ation.unity scene
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.
Hey there! Since there’s no module branch for insider threat, I’m a little unsure if it’s the best idea to merge it directly into the main branch. The ProjectStructure.docx actually suggests against merging into the main branch initially. If anyone who’s going to approve it isn’t sure, please feel free to reject it, and I’m happy to create the module for insider threat if needed!