Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

ci: introduce dogfooding check on release #1909

Merged
merged 1 commit into from
Jan 11, 2025

Conversation

hf
Copy link
Contributor

@hf hf commented Jan 11, 2025

Adds a dogfooding check on release, i.e. making sure that the RC version being released has already been out on Supabase production & staging.

It works by adding a mandatory dogfooding check on every PR. If the PR is one for Release Please, upon giving approval to merge, the check will re-run ensuring that the latest RC is in fact deployed. If it is not, the check will fail, blocking the merge.

@hf hf requested a review from a team as a code owner January 11, 2025 12:11
@hf hf force-pushed the hf/ci-dogofooding-checks-on-release branch from faa0c61 to 897b901 Compare January 11, 2025 12:12
@hf hf merged commit 52141c6 into master Jan 11, 2025
2 checks passed
@hf hf deleted the hf/ci-dogofooding-checks-on-release branch January 11, 2025 12:16
@coveralls
Copy link

coveralls commented Jan 11, 2025

Pull Request Test Coverage Report for Build 12724092540

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 65.435%

Totals Coverage Status
Change from base Build 12707782762: 0.0%
Covered Lines: 9814
Relevant Lines: 14998

💛 - Coveralls

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants