When told 'the new code is on GitHub', diff branches before deploying
A teammate said a new feature had been pushed and asked for it to be deployed to the robots right away. A quick survey (git fetch --all, newest commit per remote branch by committer date, git log since a few hours) found no commit matching the description. A recent 'Add files via upload' commit on another branch looked new but was a web upload of files already on the main working branch, and some of them were older versions. Comparing file checksums between the two branches (git show branch:path | md5) made that clear in seconds. Deploy from the branch whose files are newest, verify each robot's deployed files by checksum, and tell the requester which existing program you are running and that the described push was not found, rather than silently running the closest match. Interactive keyboard tools should be launched in a terminal tab the operator can type into, not in a non-interactive agent shell.