Apologies for coming back to this. NO OFFENCE INTENDED.
today I rebuild a test system, following the instructions provided.
I ran pihole checkout ftl new/CNAME_inspection_details, when this completed I ran pihole checkout web new/CNAME_inspection_details
As you can see, the second command failed:
pi@raspberrypi:~ $ pihole checkout ftl new/CNAME_inspection_details
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
[✓] Branch new/CNAME_inspection_details exists
[✓] Downloading and Installing FTL
[✓] Restarting pihole-FTL service...
[✓] Enabling pihole-FTL service to start on reboot...
pi@raspberrypi:~ $ pihole checkout web new/CNAME_inspection_details
Please note that changing branches severely alters your Pi-hole subsystems
Features that work on the master branch, may not on a development branch
This feature is NOT supported unless a Pi-hole developer explicitly asks!
Have you read and understood this? [y/N] y
[i] Fetching branches from https://github.com/pi-hole/AdminLTE.gitfatal: unable to access 'https://github.com/pi-hole/AdminLTE.git/': Could not resolve host: github.com
[✗] Fetching branches from https://github.com/pi-hole/AdminLTE.git
Again, this was caused by pihole-FTL simply NOT ready to resolve (Could not resolve host: github.com).
I really think, using the countdown timer routine, already in the code, to prevent resolver timeouts, whenever pihole-FTL is starting / reloading / … would improve pihole's reliability.
Unfortunately, nobody else appears to have a problem with this...