Here's one that took me a surprising amount of digging to find an answer deep in a lone comment in a thread.
You're running your chrome/chromedriver-driven test suite and start getting mysterious errors, which might be related to problems that were previously solved by setting particular options. After some . . .
Sometimes after rebasing and force pushing, github will show commits in a different order from what you expect.
git rebase -i master --exec 'git commit --amend --date="$(date -R)"' git push --force origin my-branch
If I remember correctly, some solutions to this problem . . .
- Confident Ruby https://shiprise.dpdcart.com/
- Objects on Rails https://shiprise.dpdcart.com/
- Working With UNIX Processes https://www.jstorimer.com/pages/books
- Working With Ruby Threads https://www.jstorimer.com/pages/books
- Don’t Make Me Think http://sensible.com/dmmt.html . . .
git clone --mirror old-remote-url cd repo.git git push --mirror new-remote-url
Measure the time taken to perform each type of job
I put this in my lib directory:
class SidekiqMetrics def call(worker, msg, queue) librato_queue = Librato::Metrics:: . . .
How to make a git branch be based off of a different branch from what it was originally branched off from
An easy thing to do covered confusingly in 2-dozen other blog posts around the web. But not here my friend.
git checkout branch-you-are-working-on git rebase --onto branch-you-want-it-based-on branch-it-is-based-on