From 32bdc5d1900ceb8df1e8ee33ea65af7b4da61051 Mon Sep 17 00:00:00 2001 From: Eduardo San Martin Morote Date: Fri, 3 Nov 2023 17:14:07 +0100 Subject: [PATCH] chore: typo [skip ci] --- .github/maintenance.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/maintenance.md b/.github/maintenance.md index e080dbcf719..8d4317c6b01 100644 --- a/.github/maintenance.md +++ b/.github/maintenance.md @@ -40,7 +40,7 @@ Depending on the type of the PR, different considerations need to be taken into #### Verifying a Fix - **Always locally verify that the fix indeed fixes the original behavior, either through a reproduction or a failing test case.** -- We will run [ecosystem-ci](https://github.com/vuejs/ecosystem-ci) before every release, but if you are concerned about the potential impact of a change, it never hurts to manually run ecosystem-ci` by leaving a `/ecosystem-ci run` comment (only works for team members). +- We will run [ecosystem-ci](https://github.com/vuejs/ecosystem-ci) before every release, but if you are concerned about the potential impact of a change, it never hurts to manually run ecosystem-ci by leaving a `/ecosystem-ci run` comment (only works for team members). - Take extra caution with snapshot tests! The CI can be "passing" even if the code generated in the snapshot contains bugs. It's best to always accompany a snapshot test with extra `expect(code).toMatch(...)` assertions. ### Reviewing a Refactor