action-label-syncer VS probot-auto-merge

This is when we strongly felt the need to sync/orchestrate labels across all the repositories while also respecting the differences between the projects (one size may not fit all). This led us to a proof of concept with different label syncing tools and after quite a bit of analysis, we landed on Label Syncer to manage both master and repository level declarative labels (If someone from Github is reading this, maybe this should be an inbuilt feature 😇)

For me, automating the management of issue labels on GitHub was a small but important step to achieve consistency across my repositories. Many different tools exist to either sync or create labels, and after evaluating a few my choice fell on Label Syncer. Most importantly, its fully configured in code and as a GitHub Action part of the repository it manages.

probot-auto-merge can be customized quite heavily, but the above is the minimal configuration that is required to automatically merge Dependabot's pull requests. It instructs probot-auto-merge to merge any pull request with the label PR-merge, and report the status of its runs as a check on the pull request. The latter is not required, but very helpful to understand and debug the configuration.