When you see error such as this 1bash-4.1$ git checkout Brick_Release_2018-06-19 2error: pathspec 'Brick_Release_2018-06-19' did not match any file(s) known to git. 'git fetch' first and retry to checkout. If it still fails, ensure you're using the correct branch name.

1$ git remote set-url --push origin no-pushing 2$ git push 3fatal: 'no-pushing' does not appear to be a git repository 4fatal: The remote end hung up unexpectedly See https://stackoverflow.com/questions/7556155/git-set-up-a-fetch-only-remote

Scenario: A PR has been merged and further tests found out that it breaks the build. What do you do? 1git checkout -b to-revert-commits 2git revert <sha-to-remove> 3git push -u origin to-revert-commits 45## create a Pull Request and have it reviewed and merged by others.

See https://github.com/blog/2019-how-to-undo-almost-anything-with-git

1create database yourDB; 2CREATE USER 'yourDBA'@'localhost' IDENTIFIED BY 'yourPASS'; 3GRANT ALL PRIVILEGES ON yourDB.* TO 'yourDBA'@'localhost'; 4FLUSH PRIVILEGES;

Use format below: 1GRANT ALL ON yourDB.* TO yourDBA@'23.216.39.44' IDENTIFIED BY 'yourPASS'; and make sure that 'bind-address' in /etc/my.cnf is either 0.0.0.0 or commented out for this to take effect. Turn-off as well any firewall, SELinux, etc. Further details in …

If you see an error like the following: 1ERROR 2006 (HY000): MySQL server has gone away 2No connection. Trying to reconnect... 3Connection id: 990 4Current database: yourDB Add the the following to /etc/my.cnf, increasing the value if error persists. 1'max_allowed_packet=64M' See …