Allow direct GitHub communication in devcontainer #50
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.
Marvelous!
We can now operate in the container and communicate with GitHub.
2 issues arose in development:
So in the end, we're falling back to communicating through HTTPS. It's better than before. In the past, I would operate in VS Code for development and switch back to the Terminal on my host machine for committing and interacting with GitHub since the container didn't have the right permissions to do so.
What we'll do is open separate feature tickets to allow for each individual feature to work in the future. I don't want to enforce an engineer/team on how they wish to interact with GitHub. The template is there to enable people and they can decide in which direction that they want to head.