Letting orgs customize or provide an alias to stock GH App triggers will ease adoption for orgs that having long standing labels embedded in their system. For example, an org may use a Github webhook to trigger a CircleCI build with the label, configured under a machine user. They would like to ensure that the underlying Github user working on a PR (that could apply label and trigger a build) would be associated as the author of the new pipeline. GH App adoption would solve for this BUT would require the entire org to update their label from to for it to work. An easier path to adoption would get orgs to take advantage of new features and functionality.