Prem Sichanugrist

I know that for RubyGems if you do `gem push` from command line you'll need to do 2FA to approve it. However, I assume those goes away once more and more gems move to use GitHub Actions to release the gem?

I wonder if RubyGems or gem.coop would add this to the flow?

https://docs.npmjs.com/staged-publishing

Huh Mastodon doesn't actually show GitHub commit's preview? 🤔

Just realized I could do `git rebase --interactive GIT_REF~1` after `git commit --fixup GIT_REF` so I here present you `gfuu` so you could do fixup and squash them up in a single step https://github.com/sikachu/dotfiles/commit/5893d5394751086174cd035e9835c45c46384128

Usage: `gfuu GIT_REF`

#git

@Schneems@ruby.social I really like the idea. However, I'd like to also suggest adding an ability for authors to hide prior gems from their profile as well. In Rails case, I remember there were a few contributors who asked to "dissociated" them from Rails and remove their names from Rails Alumni page. I felt like some people might feel strongly about having project that they left on a bad term still show up on their profile. What do you think?

The line for SmartBank’s #rubykaigi_hackspace ticket distribution was pretty crazy 😂. I am glad I was able to secure a ticket.

#rubykaigi

I'm not going to miss having to write +code+ instead of `code` inside Ruby documentations

#rubykaigi #rubykaigiA

Learning about FFI from @tenderlove@mastodon.social

#rubykaigi #rubykaigiA

Still 3 left to go for all perfect, but decided to claim my prize now 😂

@siracusa@mastodon.social I really enjoyed the portion in the latest special episode where you tried to correct @marcoarment@mastodon.social on how he pronounced the word “enum”, so I have an #askatp question:

Would you mind asking @marcoarment@mastodon.social to pronounce these words on-air?
- enum
- numeric type
- number pad

Thanks!

@connected sending a virtual head shaking for that “let them be cook” joke 🙂‍↔️

RE: @zekjur@mas.to

I'm not a fan of code fence (which was introduced by GFM) in Git commit message anyway because it's supposed to be plaintext. Four spaces indent for code block is much better.

I guess I have one more reason to discourage it.

Does anybody know why RuboCop suggested specifying development dependencies in Gemfile instead of in gemspec file as the default behavior?

I know that RubyGems.org shows development dependencies as well, so isn't that kind of defeating the purpose?

https://docs.rubocop.org/rubocop/cops_gemspec.html#gemspecdevelopmentdependencies

@nateberkopec@mastodon.social I think nowadays if you charge your iOS device with a slow charger it'll actually tell you. They just need to port that to macOS. But yeah, that Qi stuff is also "fun" problem...

RE: @daringfireball@mastodon.social

I wonder how long before Apple will release a patch to yell at you for "No, you can't use this non-PD charger, especially USB-A to USB-C."