2034 automate port forwarding for GitHub codespaces using gh cli #2035
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.
Pull Request Type
Relevant Issues
resolves #2034
What is in this change?
This pull request introduces an automation for port forwarding in GitHub Codespaces using the gh CLI tool. Specifically, it updates the
devcontainer.jsonto install the gh CLI tool and modifies thetasks.jsonfile to poll the port until it’s redirected and apply the public property using the gh CLI. This change simplifies the development experience for GitHub Codespaces users by automating the port forwarding process.Additional Information
This change is a follow-up to the existing documentation in the .devcontainer/README.md file, which mentions the need to manually set the port visibility to “Public” when running the server for the first time in GitHub Codespaces. This automation eliminates the need for manual configuration and improves the reliability and consistency of the development environment. NOTE: I've not updated the readme in this PR.
Developer Validations
yarn lintfrom the root of the repo & committed changes - (N/A).devcontainer/readme.md