@jkreeftmeijer I tend to do: `git push heroku HEAD:master`, which deployed the current branch I'm on.
Deploying a branch that’s not called `master` to Heroku (or pushing to a different branch name on remote in general)? Remembering to prefix the remote’s branch name with the local one might save you some confusion.
$ git push heroku my_branch:master
Where `heroku` is the remote, `my_branch` is the local branch name, and `master` is the remote branch name. Hopefully, I’ll get it right on the first try too, one day.
This. Also, don't require logging in (you can figure out the e-mail address), and don't ask which types of marketing e-mails they'd like to unsubscribe from. Unless, of course, if your app sends notifications the user actually signed up for.
“🌞 Sun With Face. A yellow sun with a kind, smiling face. Not your typical smiling sun with big grin and sunglasses.” #notyourtypicalsun
“`rand()` is your friend.” #euruko2019
“If Ruby dies, my family will die.” #euruko2019
Obligatory “I’m on a boat” update. 🚢 #euruko2019
My current article series is based around writing an example application. As an experiment, I’m writing most of the draft in ~250-word commit messages in the example repository (https://github.com/jeffkreeftmeijer/hayago/commits/master).
To get a very rough outline for the first article, I printed the commit message bodies to a markdown file in reverse.
$ git log --reverse --pretty=format:%b > draft.md
Thursday already? That means it’s time for largely-instrumental-progressive-rock-and-math-rock-bands weekly! This week, check out Chon’s new self-titled album, which came out this month. 🎸 https://open.spotify.com/album/31xSTnqna5WeOdCN0AJMNJ?si=CecIHuJBTgGNAy1Hbmytxw
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!