<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.--> ### Proposal Like many of our peers in the industry we've been adding prefixes to some of our tokens (personal/project/group access tokens, runner registration tokens). Next in line for this effort would be the pipeline trigger tokens. We've had issues in the past where such tokens were leaked and adding a prefix would help our detection mechanisms and help our security teams detect and prevent leaks more effectively. I suggest a `glptt-` (`ptt` for **p**ipeline **t**rigger **t**oken) prefix but it can be anything as long as it's easy to search for! <!-- Use this section to explain the feature and how it will work. It can be helpful to add technical details, design proposals, and links to related epics or issues. --> <!-- Consider adding related issues and epics to this issue. You can also reference the Feature Proposal Template (https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md) for additional details to consider adding to this issue. Additionally, as a data oriented organization, when your feature exits planning breakdown, consider adding the `What does success look like, and how can we measure that?` section. --> <!-- Label reminders Use the following resources to find the appropriate labels: - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->