Skip to content

fix: GetGitRoot stuck#54

Merged
soedirgo merged 2 commits into
mainfrom
fix/git-root
Oct 18, 2021
Merged

fix: GetGitRoot stuck#54
soedirgo merged 2 commits into
mainfrom
fix/git-root

Conversation

@soedirgo
Copy link
Copy Markdown
Member

Fixes #53.

@soedirgo soedirgo merged commit fb935d1 into main Oct 18, 2021
@soedirgo soedirgo deleted the fix/git-root branch October 18, 2021 04:04
@github-actions
Copy link
Copy Markdown

🎉 This PR is included in version 0.10.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

dumko2001 pushed a commit to dumko2001/cli that referenced this pull request Mar 15, 2026
kallebysantos pushed a commit to kallebysantos/supabase-cli that referenced this pull request May 6, 2026
## What kind of change does this PR introduce?

This adds e2e test coverage for four `domains` commands and the option
to run parity tests with handwritten fixtures.

We can't really test the `domains` commands against staging, since we'd
have to set up actual DNS records to verify the happy path — so we're
using handwritten fixtures (recorded with Proxyman) for the happy path
and recorded responses for the unhappy path ("custom domain not
enabled").

I encountered two blockers here:

- The parity checks should probably test `domains get`, which is
scenario based – that's why I added scenario support to `testParity`
- The `domains create` commands first verify CNAME records by querying
`1.1.1.1`. IIUC, we can only mock that at the OS level, since it's
hard-coded in the Go binary — should we skip the test?

## What is the current behavior?

There was no e2e coverage for the domains commands.

Fixes CLI-1380

## What is the new behavior?

- testParity now supports scenarios
- `domains get` has behavior and parity tests for `--output json`
- `domains get` has coverage for various error paths (400, 401, 403,
429, 500, 502)
- e2e tests for `domains` commands based on various states:
  - Custom Domains not enabled
  - Custom Domains enabled, but no Custom Domain set
  - Custom Domain set, but verification pending
  - Custom Domain set & verified, but not activated
  - Custom Domain activated
@supabase-cli-releaser supabase-cli-releaser Bot mentioned this pull request May 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

'supabase init' stalls macOS Big Sur 11.6

1 participant