From 6b1d992976a190b467ca5f9cfb390e82f5c72ce3 Mon Sep 17 00:00:00 2001 From: Axel Lorens <54468493+RheuX@users.noreply.github.com> Date: Thu, 10 Oct 2024 15:14:46 -0700 Subject: [PATCH] update vi-github-issues.md (fixes #3393) (#3395) --- pages/vi/vi-github-issues.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/vi/vi-github-issues.md b/pages/vi/vi-github-issues.md index f9ca85365..4222cf64c 100644 --- a/pages/vi/vi-github-issues.md +++ b/pages/vi/vi-github-issues.md @@ -30,7 +30,7 @@ If you've noticed an area for improvement in the Software Engineering Virtual In **Note**: While creating a Pull Request doesn't require prior approval, it's best to wait for confirmation of the issue from our team before working on a fix. If your suggested changes don't align with project goals, your Pull Request might not be merged, and your work won't count toward "First Steps" progress. By seeking approval first, you can avoid wasted effort and rework. -**Existing Issues:** You can also work on existing issues. If an issue is labeled `mi` and `first step intern`, you can request to work on it by messaging us in Discord. If someone else is already assigned or has stated their intent to work on it in the issue's comment section, don't work on that issue; choose another one instead. +**Existing Issues:** You can also work on existing issues. If an issue is labeled `vi` and `first step intern`, you can request to work on it by messaging us in Discord. If someone else is already assigned or has stated their intent to work on it in the issue's comment section, don't work on that issue; choose another one instead. _**Special Note**_: - Interns often rush through this process to complete their "First Steps." Remember that these steps aim to fix genuine problems and improve the workflow. Take time to examine the "First Steps" materials to find real issues and research the best solutions. Also, ensure the issue hasn't already been identified.