We have a Waffle board which is awesome to keep track of everything that is going on in the repositories of the DSC Resource Kit.
There is some automation that is done by thanks to the Waffle board. Writing it here so it can be added to a new automation markdown file later.
In the Waffle board it's possible to drag issue/PR to different columns and that way automatically label them. I don't think it is necessary to document that, since it basically the same as anyone labeling the issue or PR directly, and the issue or PR will move to the Waffle board column automatically, so not an automation per say. Although, it is one difference if the Waffle board or user changes a label. There is a property isBot that is set to true in the returned payload (for webhooks) if there was a bot that did the change. That can affect how other bot threats the label change if it is done by the Waffle board or done by a user.
There is a automation when issues are closed, or PR's are close or merged. When an issue is closed and the issue is in any of the Waffle board columns (except the Backlog or Done column), the assigned label to that column is removed. Same happens when a PR is merged or closed.
For example if an issue is in the Help Wanted column on the Waffle board, then the issue will have the label help wanted assigned. If the issue is closed, the help wanted label will be removed (and the issue will be moved to the Closed column in the Waffle board).
This is the code to build the flowchart.
On pull request
close/merge,
or issue close;
// If not assigned it will be
// in the Backlog column
// -
// **Waffle columns**
// -
// **Issue columns:**
//
// blocking release
// high priority
// help wanted
// questions
// needs investigating
// discussion
// needs more information
// new module submission
// module proposal
// -
// **PR columns:**
// waiting for CLA
// abandoned
// needs review
// ready to merge
// in progress
// waiting for code fix
// waiting for author response
// -
// **Issue and PR columns:**
// on hold
if(Is assigned to
a column?)
{
// Normally the column
// name is the same as
// the label name.
Remove all labels
assigned to the
issue that have
a column on the
Waffle board;
}
Finished;
We have a Waffle board which is awesome to keep track of everything that is going on in the repositories of the DSC Resource Kit. There is some automation that is done by thanks to the Waffle board. Writing it here so it can be added to a new automation markdown file later.
In the Waffle board it's possible to drag issue/PR to different columns and that way automatically label them. I don't think it is necessary to document that, since it basically the same as anyone labeling the issue or PR directly, and the issue or PR will move to the Waffle board column automatically, so not an automation per say. Although, it is one difference if the Waffle board or user changes a label. There is a property
isBot
that is set totrue
in the returned payload (for webhooks) if there was a bot that did the change. That can affect how other bot threats the label change if it is done by the Waffle board or done by a user.There is a automation when issues are closed, or PR's are close or merged. When an issue is closed and the issue is in any of the Waffle board columns (except the Backlog or Done column), the assigned label to that column is removed. Same happens when a PR is merged or closed. For example if an issue is in the Help Wanted column on the Waffle board, then the issue will have the label help wanted assigned. If the issue is closed, the help wanted label will be removed (and the issue will be moved to the Closed column in the Waffle board).
This is the code to build the flowchart.