From 76b61d013530276cd8ce1262005a6882b286a304 Mon Sep 17 00:00:00 2001 From: y8a5y Date: Mon, 22 Dec 2025 10:40:40 +0100 Subject: [PATCH] fix(Contrib file): add steps to ensure successful CI --- CONTRIBUTING.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3501deab4..d192d3d50 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -82,4 +82,14 @@ git commit -m "fix(homepage): fix typo on homepage in the faq section" It helps to be as descriptive as possible in commit messages so that users can be aware of the changes made by you. +Then, you can run the basic checks, as to make sure the CI has the most chance of being successful: + +``` +pnpm run lint + +pnpm run test + +pnpm run build +``` + Finally, create a pull request to merge the changes on your forked repository to the original repository hosted on AmruthPillai/Reactive-Resume. I can take a look at the changes you've made when I have the time and have it merged onto the app.