Skip to content

Conversation

@Kavignon
Copy link
Contributor

Marvelous!

We can now operate in the container and communicate with GitHub.

2 issues arose in development:

  • I couldn't mount my SSH public keys in the container
  • I couldn't automatically installed the binaries for gh

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.

@Kavignon Kavignon added enhancement New feature or request Devcontainer Fixing or updating a feature in development container Containerization Issue relates with dev or production container IDE config Relates to the VS Code configuration Terminal config Relates to terminal configuration labels Dec 14, 2024
@Kavignon Kavignon self-assigned this Dec 14, 2024
@Kavignon Kavignon merged commit 7a7b8b4 into main Dec 14, 2024
37 checks passed
@Kavignon Kavignon added this to the ver 1.0.0 milestone Dec 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Containerization Issue relates with dev or production container Devcontainer Fixing or updating a feature in development container enhancement New feature or request IDE config Relates to the VS Code configuration Terminal config Relates to terminal configuration

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants