From: Eduardo San Martin Morote Date: Fri, 3 Nov 2023 16:14:07 +0000 (+0100) Subject: chore: typo [skip ci] X-Git-Tag: v3.3.8~6 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=32bdc5d1900ceb8df1e8ee33ea65af7b4da61051;p=thirdparty%2Fvuejs%2Fcore.git chore: typo [skip ci] --- diff --git a/.github/maintenance.md b/.github/maintenance.md index e080dbcf71..8d4317c6b0 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