Introduce REST API fallback

Switch to using the GitHub REST API as a fallback when HTML parsing
fails to retrieve the commit hash from the GitHub commits page. This
ensures that the script continues to work even under rate limit
conditions and improves reliability. Optionally, authentication can
be used to further mitigate rate limits.

Co-authored-by: Po-Ying Chiu <[email protected]>
Change-Id: If204a6c78bb4062bc010c3370db0ea126f99e6f5

Author: EricccTaiwan

scripts/check-repo.sh

@@ -85,6 +85,22 @@ upstream_hash=$(
 
 rm -f "$temp_file"
 
+# If HTML parsing fails, fallback to using GitHub REST API
+if [ -z "$upstream_hash" ]; then
+  echo "HTML retrieval failed, falling back to GitHub REST API..."
+  API_URL="https://api.github.com/repos/${REPO_OWNER}/${REPO_NAME}/commits"
+  
+  # Optional: Use authentication to avoid rate limit issues.
+  # Uncomment the following line and replace YOUR_ACCESS_TOKEN with your actual token.
+  # response=$(curl -sSL -H "Authorization: token YOUR_ACCESS_TOKEN" -H "Accept: application/vnd.github+json" -H "User-Agent: YourAppName" "$API_URL")
+  
+  # Without authentication:
+  response=$(curl -sSL "$API_URL")
+  
+  # Extract the latest commit SHA from the JSON response
+  upstream_hash=$(echo "$response" | grep -m 1 '"sha":' | sed -E 's/.*"sha": "([^"]+)".*/\1/')
+fi
+
 if [ -z "$upstream_hash" ]; then
   throw "Failed to retrieve upstream commit hash from GitHub.\n"
 fi