Repository navigation
- adds documentation for issues automation - #3454
Conversation
lornajane
left a comment
There was a problem hiding this comment.
Thanks for adding this information! I think it needs to go a lot further down the page since the automation (while excellent) is not key to our mission - perhaps between Transparency and Participation? Also is there a way we can condense the diagram, it's more than a whole screen tall for me and while it's a good representation of how the code works, I'm not sure this is the information that users need.
I'd be tempted to add a list of the labels and what they mean.
- adds labels descriptions Signed-off-by: Vincent Biret <vibiret@microsoft.com>
|
just pushed some changes to implement the suggestions. |
|
ping @lornajane |
|
Thanks for moving the information to a better location in the document. I'm still not sure the mermaid diagram adds a lot for the amount of screen space it takes - the label descriptions are very good though! |
|
@lornajane did you see my suggestion to adding a new page dedicated to the diagram? |
|
I don't feel strongly about it - probably nobody would look at the diagram if we moved it, so maybe we can just remove it and see how we get on. One question, when I reply to an issue that has "needs attention", do I manually remove that label when I do that? |
|
To answer your question: yes when you reply you manually need to remove the "needs attention" label and add the "needs author feedback" one. We could also automate that, but I'd need a list of "experts" GitHub handle for the people who qualify for this automation (we don't want it to trigger for everyone). Ok I'll remove the diagram, I found it's usually a good way to help people understand the logic of a workflow rather than lots of text. |
|
updated. I also added information to when labels are added removed in their descriptions since we don't have the diagram anymore. |
fixes #3452