Is your improvement proposal related to a problem? Please describe.
Currently, Semaphore CI only supports triggering workflows from branches and tags for GitLab repositories. This limitation prevents users from accessing crucial pull request information during a build, such as the pull request number. As a result, automated tasks that rely on this data—like posting static code analysis results or other feedback directly to a pull request—are not possible.
To improve workflow efficiency and collaboration for users who integrate with GitLab, we need to add native support for pull request triggers. This feature would allow workflows to automatically run when a new pull request is opened or updated, making it possible to post build statuses and analysis reports back to the corresponding pull request in Bitbucket.
Describe the solution you'd like
TBD
Describe alternatives you've considered
TBD
Additional context
No response
Is your improvement proposal related to a problem? Please describe.
Currently, Semaphore CI only supports triggering workflows from branches and tags for GitLab repositories. This limitation prevents users from accessing crucial pull request information during a build, such as the pull request number. As a result, automated tasks that rely on this data—like posting static code analysis results or other feedback directly to a pull request—are not possible.
To improve workflow efficiency and collaboration for users who integrate with GitLab, we need to add native support for pull request triggers. This feature would allow workflows to automatically run when a new pull request is opened or updated, making it possible to post build statuses and analysis reports back to the corresponding pull request in Bitbucket.
Describe the solution you'd like
TBD
Describe alternatives you've considered
TBD
Additional context
No response