automatic test domain deployments have reference: "main" not "live-test"

[PietrH]

I've noticed that the version deployed via the trigger on the test domain is the version of the package on main, not the one from live-test as is the intention. You can tell by the hash during the install output.

This blocks testing the API really as I need to have my changes on main in order for it to get deployed to the test env.

For deployments to the production domain I still need to email Paul, so users are actually relatively safe from unexpected changes. But since etnservice is a dependency of v2.3.0+ etn, I still need to be able to deploy a test branch from a different place as main.

This blocks #73, #76 and future feature work like the new sql views.

[PietrH]

automatic deployments are failing at the moment because of Github API rate limiting, also etn doesn't need to be installed. Only arrow and etnservice;

{"id": "", "status": "completed", "start_timestamp": "2025-09-30T09:09:16.593753+00:00", "end_timestamp": "2025-09-30T09:09:18.662854+00:00", "result": ["Error: Failed to install 'etn' from GitHub:\n HTTP error 403.\n API rate limit exceeded for . (But here's the good news: Authenticated requests get a higher rate limit. Check out the documentation for more details.)\n\n Rate limit remaining: 0/60\n Rate limit reset at: 2025-09-30 09:13:52 UTC\n\n To increase your GitHub API rate limit\n - Use `usethis::create_github_token()` to create a Personal Access Token.\n - Use `gitcreds::gitcreds_set()` to add the token.\nExecution halted\n", 500], "error": null}