🌈 Rich Label Workflows

That's how your repositories are going to look from now on!

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/8a8d6926-0226-4ca3-a170-d587999466ad/issues.png

🤖 Instant feedback about the changes

LabelSync by default comments on every commit and pull request in your configuration repository. This way you don't have to worry about accidentally breaking something.

https://s3-us-west-2.amazonaws.com/secure.notion-static.com/7f4a768c-a002-4dd0-bd51-c7cbacfd7d99/pr-comment.png

🎢 LabelSync's Siblings

Paid accounts may create workflows using LabelSync's siblings.

Each label in your configuration can reference multiple siblings. Whenever you add a label to an issue or pull request, LabelSync will automatically add all the missing siblings as well.

<aside> 💡 For example, you could configure multiple stages of bugs (bug/0-norepro, bug/1-repro, bug/2-confirmed) and add a sibling kind/bug to all of them. This way, whenever you add one of them to any issue labelsync bot is going to add kind/bug as well.

</aside>

Read more about them in the YAML documentation.