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

[ci] Fix the base branch we use to determine changes #79503

Merged
merged 1 commit into from
Jan 25, 2024

Conversation

ldionne
Copy link
Member

@ldionne ldionne commented Jan 25, 2024

We should diff against the base branch, not always against main. This allows the BuildKite pre-commit CI to work properly when we target other branches, such as release/18.x.

We should diff against the base branch, not always against `main`.
This allows the BuildKite pre-commit CI to work properly when we
target other branches, such as `release/18.x`.
Copy link
Collaborator

@tstellar tstellar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't know much about buildkite, but I'm in favor of this change.

@ldionne ldionne force-pushed the review/fix-base-branch-buildkite branch from 803b0bc to edf87f4 Compare January 25, 2024 21:34
@ldionne
Copy link
Member Author

ldionne commented Jan 25, 2024

Merging since this seems to work according to the pipeline generation logs.

@ldionne ldionne merged commit 3b76289 into llvm:main Jan 25, 2024
7 checks passed
@ldionne ldionne deleted the review/fix-base-branch-buildkite branch January 25, 2024 21:38
ldionne added a commit to ldionne/llvm-project that referenced this pull request Jan 25, 2024
We should diff against the base branch, not always against `main`. This
allows the BuildKite pre-commit CI to work properly when we target other
branches, such as `release/18.x`.

(cherry picked from commit 3b76289)
tstellar pushed a commit that referenced this pull request Jan 25, 2024
)

We should diff against the base branch, not always against `main`. This
allows the BuildKite pre-commit CI to work properly when we target other
branches, such as `release/18.x`.

(cherry picked from commit 3b76289)
tstellar pushed a commit to tstellar/llvm-project that referenced this pull request Feb 14, 2024
…lvm#79506)

We should diff against the base branch, not always against `main`. This
allows the BuildKite pre-commit CI to work properly when we target other
branches, such as `release/18.x`.

(cherry picked from commit 3b76289)
tstellar pushed a commit to tstellar/llvm-project that referenced this pull request Feb 14, 2024
…lvm#79506)

We should diff against the base branch, not always against `main`. This
allows the BuildKite pre-commit CI to work properly when we target other
branches, such as `release/18.x`.

(cherry picked from commit 3b76289)
tstellar pushed a commit to tstellar/llvm-project that referenced this pull request Feb 14, 2024
…lvm#79506)

We should diff against the base branch, not always against `main`. This
allows the BuildKite pre-commit CI to work properly when we target other
branches, such as `release/18.x`.

(cherry picked from commit 3b76289)
tstellar pushed a commit to tstellar/llvm-project that referenced this pull request Feb 14, 2024
…lvm#79506)

We should diff against the base branch, not always against `main`. This
allows the BuildKite pre-commit CI to work properly when we target other
branches, such as `release/18.x`.

(cherry picked from commit 3b76289)
@pointhex pointhex mentioned this pull request May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants