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.
GitHub CLI 1.0
101–110 of 221 posts
Re: GitHub CLI 1.0
#102All 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.
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
#103All 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
#104All 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)
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
#105Re: GitHub CLI 1.0
#106Is this coming full circle: Git -> GitHub -> GitHub CLI?
Re: GitHub CLI 1.0
#107This is worth it just for `gh repo create`
Re: GitHub CLI 1.0
#108Oh 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/
Re: GitHub CLI 1.0
#109What about https://hub.github.com/ ?
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
#110Earlier 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.
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 :)