I'm willing to work on a royalty share deal or a fixed fee (PFH), so I'm offering you an opportunity to submit me your work. The story that I connect with I'll do the graphic part for, finalize the audio and pay for the https://publishdrive.com/ fee so we can make some income together, even a little ;). Source: about 1 year ago

Draft2Digital. https://www.draft2digital.com. It’s for E-books. They are testing a print service and I’m still on the waiting list. Publishdrive https://publishdrive.com. Never used, but they they charge a subscription instead of taking part of your royalties. Source: over 2 years ago

PUBLISHDRIVE: Publishdrive requires a monthly payment to publish your books. You get more royalty, but it will cost more each month. There is an App sumo coupon running around if you want to try it. I would be very cautious and read the fine print. I don’t use them. They are kind of a nightmare to deal with. Source: over 2 years ago

Use hub here via CLI and forget the gui https://hub.github.com/. - Source: Hacker News / 10 months ago

Try automating the PR process as much as possible. Make use of tools like hub CLI for speeding up the pull request process. Code quality tools can help you automate the due diligence for coding standards and conventions, and test automation tools can assist in bug discovery, and identifying security vulnerabilities. - Source: dev.to / about 1 year ago

Parse_git_branch() { # Speed up opening up a new terminal tab by not # checking `$HOME` ...which can't be a repo anyway # # For the heck of it, micro-optimize this too: # time (repeat 1000000 { [ "$PWD" = "$HOME" ] } ) == ~4.2s # time (repeat 1000000 { [[ "$PWD" == "$HOME" ]] } ) == ~1.4s [[ "$PWD" == "$HOME" ]] && return # Fastest known way to check the current branch name ... Source: almost 2 years ago

You can always query via github api or use the hub client (from their home page https://hub.github.com/). Source: over 2 years ago