Repository navigation
Changes to align devcontainer with hack rules and paths - #476
Merged
Merged
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
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.
This pull request updates the Azure Fraud Intelligence hack's dev container and documentation to streamline environment setup and clarify onboarding steps for users. The main changes include removing redundant environment scripts, improving the dev container configuration, and enhancing the challenge and walkthrough instructions for clarity and usability.
Dev Container and Environment Setup Improvements:
devcontainer.json) to set a consistent name, specify the workspace folder, configure remote environment variables, switch frompostCreateCommandtopostAttachCommand, and remove the now-unnecessarypost-create.shscript. This simplifies the Codespace setup and ensures the correct environment is loaded on attach. [1] [2] [3] [4]baseenvscript, as all required environment variables are now set via other mechanisms.Documentation and Challenge Instructions:
baseenv, instructing users to only sourcehackenv, which reflects the new environment setup process. [1] [2] [3] [4] [5] [6]These changes collectively make the setup process more robust and user-friendly, reducing potential confusion for new users and ensuring a smoother onboarding experience.