Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Merge Request source and target branch available in GitLabCIPullRequestInfo #4416

Closed
2 tasks done
ap0llo opened this issue Jan 3, 2025 · 0 comments · Fixed by #4417
Closed
2 tasks done

Make Merge Request source and target branch available in GitLabCIPullRequestInfo #4416

ap0llo opened this issue Jan 3, 2025 · 0 comments · Fixed by #4417
Labels
Milestone

Comments

@ap0llo
Copy link
Contributor

ap0llo commented Jan 3, 2025

Prerequisites

  • I have written a descriptive issue title
  • I have searched issues to ensure it has not already been reported

Cake runner

Cake Frosting

Cake version

5.0.0

Operating system

Windows

Operating system architecture

x64

CI Server

GitLab CI

What are you seeing?

GitLabCIPullRequestInfo provides information about the current pull request/merge request when running in GitLab CI.

However, it does not make available the source and target branch of the Merge Request.

What is expected?

GitLabCIPullRequestInfo should provide the source and target branch, analogous to e.g. AzurePipelinesPullRequestInfo

Steps to Reproduce

N/A

Output log

N/A

Workaround

The source and target branch can be determined by reading the environment variable CI_MERGE_REQUEST_SOURCE_BRANCH_NAME respectively CI_MERGE_REQUEST_TARGET_BRANCH_NAME

@devlead devlead added this to the v5.1.0 milestone Jan 4, 2025
@devlead devlead added the Feature label Jan 4, 2025
devlead added a commit that referenced this issue Jan 4, 2025
…gitlabcipullrequestinfo

Add source and target branch to GitLabCIPullRequestInfo (#4416)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants