70696137f1961bee75cc7043ab92ea5c3798219a
lrnassar
Tue Oct 21 16:54:09 2025 -0700
Updating the text to be more general now that the API key is used with the CAPTCHA bypass and not just hubtools, refs #36428
diff --git src/hg/hgHubConnect/hgHubConnect.c src/hg/hgHubConnect/hgHubConnect.c
index 35a4fc6ebee..92148601e69 100644
--- src/hg/hgHubConnect/hgHubConnect.c
+++ src/hg/hgHubConnect/hgHubConnect.c
@@ -436,42 +436,42 @@
puts("
You have already generated an API key. If you would like to generate a new key (which revokes old keys), click 'Generate key'. To use your API key with Hubtools, copy and paste the below key to your ~/.hubtools.conf file. This is not necessary for URL use to bypass our CAPTCHA.
");
+ puts("
You have already generated an API key. If you would like to generate a new key (which revokes old keys), click 'Generate key'. To use your API key with Hubtools, copy and paste the below key to your ~/.hubtools.conf file. This is not necessary for URL use to bypass the CAPTCHA.
");
puts("
");
printf("%s\n", existingKey);
puts("
");
puts("
");
puts("
Generate an API key
");
}
else
{
- puts("
To use the hubtools up command, click 'generate key'");
- puts("
");
- printf("
Now, create a file ~/.hubtools.conf and add the key: \n", existingKey != NULL ? "block" : "none");
+ puts("
Generate an API key to bypass the CAPTCHA or use the hubtools up command");
+ puts("
");
+ printf("
To use your API key with hubtools, create a file ~/.hubtools.conf and add the key. This is not necessary for URL use to bypass the CAPTCHA.