Open josebalius opened 2 years ago
- Do we prefer one large PR with the whole API implementation or multiple PRs?
I would prefer a bunch of smaller PRs if it is all the same with you.
- Do we prefer to have multiple issues?
I'm fine with a single issue.
When we have a lot of things to work on, we often use checkboxes in a single issue like this:
etc... feel free to use them if you find it helpful to keep you organized. You are welcome to use this issue or open a new one. You can also go back and edit your first entry if you wish... totally up to you.
Thank you, @josebalius ! We appreciate your contributions!
@josebalius any progress on this?
@gsmachado I started it but never really got into it much. Are you interested in taking over the issue or in the functionality?
@josebalius I'm developing something that would need the codespaces API. If I progress with the implementation directly on the go-github repo, I will submit a PR. 😄
@josebalius do you have any branch with your preliminary code?
I have some code locally that I haven't pushed up. Are you interested in it?
Can you push up whatever you came up with?
I started with some simple implementation of codespace management. I'll post the punchlist below. Happy to split it into a new issue as well.
@gmlewis I have another branch for secret management, but still waiting on getting the CLA signed. Should I push that commit to the open PR I have, or just wait until I can get the first one merged.
Your call... whichever is most convenient for you. I'm fine either way.
The impact area was pretty small. I'll add them to the existing PR while waiting for CLA followup
Nice, also looking forward to this one. Its needed for the terraform provider
I got the CLA approved, just working through getting me added to it.
I am planning on implementing support for Codespaces, see: https://docs.github.com/en/rest/codespaces
Using this issue to track that work. A couple of questions:
Thanks!