GitHub comments instead of Figma comments (#26432)

- Clarify the why
This commit is contained in:
Noah Talerman
2025-02-18 17:13:08 -05:00
committed by GitHub
parent 683c3b3892
commit 9dc3ce850b
+1 -1
View File
@@ -84,7 +84,7 @@ Additionally:
- File stories and draft changes for making form fields in the Fleet UI consistent (fixing conventions, moving out the tooltips, etc.)
- File stories and draft changes for bringing the screen width down to 375px. (one screen at a time, in which we can squeeze it into engineering sprints as front-end only work, small stories, doesn't compete with other stuff)
>**Questions, missing information, and notes:** Take a screenshot of the area in Figma and add a comment in the story's GitHub issue. Figma does have a commenting system, but it is not easy to search for outstanding concerns and is therefore not preferred. Also, commenting in Figma, sends all contributors email notifications.
>**Questions and missing information:** Take a screenshot of the area in Figma and add a comment in the story's GitHub issue. Figma does have a commenting system, but we use GitHub issues so that all questions/conversation live in one place.
>
>For external contributors: please consider opening an issue with reference screenshots if you have a Figma related question you need to resolve.