Live data from Hacker News

GitHub CLI 1.0

github.blog

101–110 of 221 posts

Re: GitHub CLI 1.0

#101
post #85

All of GH improvements have become irrelevant for me since they vanished one of our repos. No notification, no warning, no recourse. Just gonsky. It was just a simple library we wrote to talk to a public IP2Country REST service. Pushed to GitLab, end of.

Martin from GitHub here - love to understand what happened if you have the time to point me at more details. DM's open (martinwoodward on twitter and martinwoodward at github.com on email)

Re: GitHub CLI 1.0

#102
post #85

All of GH improvements have become irrelevant for me since they vanished one of our repos. No notification, no warning, no recourse. Just gonsky. It was just a simple library we wrote to talk to a public IP2Country REST service. Pushed to GitLab, end of.

I find in situations like these that it's pretty unlikely that the person telling the story really has no idea why something bad happened to them.

You are right. I have a hunch. In the local repo there is a file that was was probably produced by running wget github.com im the repo directory. Unsure what it was meant to achieve, but accidentally pushed, it may have flagged the repo down somehow. Maybe the HTML contained some secret token?

Still, the main issue was the process how they handled it. Your build breaks. This is how we found out.

Re: GitHub CLI 1.0

#103
post #85

All of GH improvements have become irrelevant for me since they vanished one of our repos. No notification, no warning, no recourse. Just gonsky. It was just a simple library we wrote to talk to a public IP2Country REST service. Pushed to GitLab, end of.

Martin from GitHub here - love to understand what happened if you have the time to point me at more details. DM's open (martinwoodward on twitter and martinwoodward at github.com on email)

I will send the repo URL in a few hours. Thanks for following up.

Re: GitHub CLI 1.0

#104
post #85

All of GH improvements have become irrelevant for me since they vanished one of our repos. No notification, no warning, no recourse. Just gonsky. It was just a simple library we wrote to talk to a public IP2Country REST service. Pushed to GitLab, end of.

Martin from GitHub here - love to understand what happened if you have the time to point me at more details. DM's open (martinwoodward on twitter and martinwoodward at github.com on email)

This is part of the problem.

No recourse for such decisions unless you make a stink about it on an orange website or get enough likes on the website with the blue bird logo.

Re: GitHub CLI 1.0

#108
post #19
post #16

Oh wow this is great. I’ve been wanting an org mode integration with GitHub for a while, and this tool might make it easy enough for me to hack together this weekend. Basically I want to be able to pull up a buffer with a list of issues assigned to me and copy them into my org mode todo list

You can do this using Forge within Magit already! And it also works for Gitlab: https://magit.vc/manual/forge/

I've been using Emacs for a decade and still have never had to write a single package of my own. Every time I have a good idea, someone else has already implemented it.

Re: GitHub CLI 1.0

#109

What about https://hub.github.com/ ?

I use `hub sync` multiple times per day. Essential tool.

It's the only way to stay sane in a repo with multiple other developers merging PRs. Updates all of your branches in the background to the current remote version.

Re: GitHub CLI 1.0

#110
post #19

Earlier quoted context omitted.

You can do this using Forge within Magit already! And it also works for Gitlab: https://magit.vc/manual/forge/

I've been using Emacs for a decade and still have never had to write a single package of my own. Every time I have a good idea, someone else has already implemented it.

I've written a few specialisms that couldn't really be open-sourced. e.g. wiring up inf-ruby and internal dev tools to open up a rails console in dev, or generate a jwt from the auth server in the cluster.

The only package I've been ultimately responsible for is the Gruvbox theme[^1], but that was very quickly handed over to other emacsers :)

I still find it a joy to write and it's one of my more preferred rabbit holes to dive into. Maybe one day there'll be something more to share :)

[^1]: https://github.com/mrleedev/emacs-gruvbox-theme

Post reply on HN