Skip to content

Commit 68a0278

Browse files
mkArtakMSFTMackinnonBuckhalter73
authored
Update HelpWantedProcess.md (#51967)
* Update HelpWantedProcess.md Update the process to include summary comment link in the description of the issue. This is important as I have noticed some issues have a long comment list and it's hard to discover the summary comment. Here is an example where I've noticed this: #47054 * Update docs/HelpWantedProcess.md Co-authored-by: Mackinnon Buck <[email protected]> * Update docs/HelpWantedProcess.md Co-authored-by: Mackinnon Buck <[email protected]> * Update docs/HelpWantedProcess.md Co-authored-by: Stephen Halter <[email protected]> * Update docs/HelpWantedProcess.md --------- Co-authored-by: Mackinnon Buck <[email protected]> Co-authored-by: Stephen Halter <[email protected]>
1 parent 30b4214 commit 68a0278

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

docs/HelpWantedProcess.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,14 @@ This process (we'll refer to it as `help-wanted` process going forward) triggers
1010
3. As part of filling out the template, the engineer will also need to **describe a high-level design for how to approach the problem and how it can be solved**.
1111
4. When all the sections of the template are filled in, the engineer will then need to **apply one of the `Complexity: <value>` labels**, to indicate how easy / hard will it be to tackle the issue.
1212
This will help community members to find the right type of issue to contribute to.
13-
5. After posting this comment, the assigned **engineer will unassign themself** from the issue and will **replace the `help-candidate` label with `help-wanted` label**, as an indicator, that the issue is ready for the community to pick up.
13+
5. After posting this comment the assigned engineer should:
14+
- Unassign themself from the issue.
15+
- **Replace the `help candidate` label with `help wanted` label**, as an indicator, that the issue is ready for the community to pick up.
16+
- Copy the direct link to the summary comment and add the link to the bottom of the description of the issue to help with discoverability, as there can be too many comments in the issue and the summary comment may be hard to find.
17+
Here is an example comment to use:
18+
19+
```text
20+
**Summary Comment** : https://github.com/dotnet/aspnetcore/issues/51912#issuecomment-1801246403
21+
```
1422
1523
This will conclude the process.

0 commit comments

Comments
 (0)