Great question :) There are several answers to it.
1. We integrate with the GitHub Checks API and surface missing labels as a failure (similar to failed tests), which acts as a reminder to add the labels. GitLab doesn't have an equivalent to our knowledge, but we have a Docker image and a snippet of yml you can include as a build stage for a similar result.
2. We had customers ask for a JIRA integration which we are about to ship that can help with that. It creates a custom field on your JIRA instance which gets populated with your configured intents, just like GitHub labels. GitHub pull requests which reference a JIRA issue will automatically inherit its labels, meaning that if the intent was expressed at planning time, then there's no additional work to do for these.
3. When discussing with organizations who request that every pull request be linked to a ticket for the sake of reporting, it's a no brainer: would you rather file a ticket for every commit or add a label?
4. Remaining untagged pull requests can be examined and labeled directly from the product itself (making it easy to erase the pesky leftovers).
Finally, the product is indeed targeted at managers at this time, but we have plans to make it more directly useful for the engineers too.
1. We integrate with the GitHub Checks API and surface missing labels as a failure (similar to failed tests), which acts as a reminder to add the labels. GitLab doesn't have an equivalent to our knowledge, but we have a Docker image and a snippet of yml you can include as a build stage for a similar result.
2. We had customers ask for a JIRA integration which we are about to ship that can help with that. It creates a custom field on your JIRA instance which gets populated with your configured intents, just like GitHub labels. GitHub pull requests which reference a JIRA issue will automatically inherit its labels, meaning that if the intent was expressed at planning time, then there's no additional work to do for these.
3. When discussing with organizations who request that every pull request be linked to a ticket for the sake of reporting, it's a no brainer: would you rather file a ticket for every commit or add a label?
4. Remaining untagged pull requests can be examined and labeled directly from the product itself (making it easy to erase the pesky leftovers).
Finally, the product is indeed targeted at managers at this time, but we have plans to make it more directly useful for the engineers too.