Rename to gel

[diksipav]

No description provided.

[diksipav]

I'm not sure these paths should be updated. In JS we run tests only on ubuntu.

[nsidnev]

Won't this break existing projects that use this action? If I would want to fix something in edgedb-elixir after merging this PR, will I need to fix my CI (and project scripts used by it) as well? I'm not sure that's what we want in the end

I'm not sure exactly how GitHub Actions behaves, but there are several things I'd like to clarify here:

1. If we change the repository to gel/setup-gel, then will projects that still use edgedb/setup-edgedb break or will GitHub redirect them automatically to gel/setup-gel
2. If it breaks on rename, then we should probably leave this action in its current state under edgedb GitHub org, just freeze it (mark as read-only) and add to the readme that the project is now called Gel and up-to-date version of this action could be found there
3. If GitHub automatically handles those redirects correctly, then this action should keep the configuration for EdgeDB (both edgedb-server and edgedb CLI executables) on par with Gel for some time (probably a long time)

[diksipav]

@nsidnev yes I agree we should probably not update this action here. I used gel for the CLI commands in my tests but reverted them now to use edgedb and the current setup-edgedb. Initially I thought that maybe there is a problem with the action, but everything works fine when using edgedb for the CLI, so I guess we can continue with that for now.

[scotttrinh]

If we change the repository to gel/setup-gel, then will projects that still use edgedb/setup-edgedb break or will GitHub redirect them automatically to gel/setup-gel

We absolutely should test this scenario during our testing of the org rename. cc @diksipav

If it breaks on rename, then we should probably leave this action in its current state under edgedb GitHub org, just freeze it (mark as read-only) and add to the readme that the project is now called Gel and up-to-date version of this action could be found there
If GitHub automatically handles those redirects correctly, then this action should keep the configuration for EdgeDB (both edgedb-server and edgedb CLI executables) on par with Gel for some time (probably a long time)

Based on the current best practice for GitHub Actions I believe we should publish a new major version and expect that no-one uses a bare or master/main specifier in their action. If they do, they'll need to update it to pin it to v1 (or better: a specific commit).

---

But yeah, step 1 is to figure out what exactly happens when a GitHub action changes both orgs and is renamed.