GitHub’s engineering team has moved to Codespaces

Re:GitHub’s engineering team has moved to Codespaces by grepfru_it on Wednesday August 11, 2021 @09:01PM (#28150369)

If you wish to leverage the advanced features of github, the CLI gives you direct access rather than rolling your own api client. git will always be a first class citizen at GIThub.. but how do you open, close, or comment on PRs with a standard git client?

Edit: The last part came across a bit snarky, but I’m trying to stimulate the thought process. Such as leveraging GitHub Actions to automate all aspects of PRs via gitops instead of using the GitHub client. Many ways to avoid dependence of the CLI!

[ Parent | on HN ]

Re:GitHub’s engineering team has moved to Codespaces by Ygg2 on Thursday August 12, 2021 @04:59AM (#28153813)

As another commenter pointed out, we're at extend part of embrace, extend, extinguish. This part is just making Github tools work easier than non Github.

In extinguish phase - Git won't prevent GitHub from rejecting a commit if it doesn't contain <TrackingMethodSignature>.

[ Parent | on HN ]

Re:GitHub’s engineering team has moved to Codespaces by rhn_mk1 on Thursday August 12, 2021 @03:17AM (#28153066)

That sounds very much like the "extend" part of the process.

[ Parent | on HN ]

Re:GitHub’s engineering team has moved to Codespaces by robertlagrant on Thursday August 12, 2021 @05:27AM (#28154013)

It feels like an open source standard on top of git that defines how to do this stuff would be helpful to reduce lockin. I wonder if Fossil or Gitlab have something.

[ Parent | on HN ]