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(psalm): Add missing imagick extension #48921

Merged
merged 1 commit into from
Oct 28, 2024

Conversation

provokateurin
Copy link
Member

Summary

Stops psalm from failing on our runners with the new 24.04 image.
Should this be backported as well and if yes down to which version?

Checklist

@provokateurin provokateurin added bug 3. to review Waiting for reviews labels Oct 28, 2024
@provokateurin provokateurin added this to the Nextcloud 31 milestone Oct 28, 2024
@provokateurin provokateurin requested review from nickvergessen, kesselb, a team, Altahrim, skjnldsv and come-nc and removed request for a team October 28, 2024 08:15
Copy link
Member

@nickvergessen nickvergessen left a comment

Choose a reason for hiding this comment

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

🙈

@provokateurin
Copy link
Member Author

@nickvergessen can you force merge?

@nickvergessen nickvergessen merged commit 988b600 into master Oct 28, 2024
177 of 179 checks passed
@nickvergessen nickvergessen deleted the ci/psalm/imagick-extension branch October 28, 2024 14:49
@provokateurin
Copy link
Member Author

/backport to stable30

@provokateurin
Copy link
Member Author

/backport to stable29

@provokateurin
Copy link
Member Author

/backport to stable28

@provokateurin
Copy link
Member Author

/backport to stable27

@provokateurin
Copy link
Member Author

/backport to stable26

@provokateurin
Copy link
Member Author

/backport to stable25

Copy link

backportbot bot commented Oct 29, 2024

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27

# Create the new backport branch
git checkout -b backport/48921/stable27

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 3a39f4a6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/48921/stable27

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Copy link

backportbot bot commented Oct 29, 2024

The backport to stable29 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable29
git pull origin stable29

# Create the new backport branch
git checkout -b backport/48921/stable29

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 3a39f4a6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/48921/stable29

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Copy link

backportbot bot commented Oct 29, 2024

The backport to stable25 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable25
git pull origin stable25

# Create the new backport branch
git checkout -b backport/48921/stable25

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 3a39f4a6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/48921/stable25

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Copy link

backportbot bot commented Oct 29, 2024

The backport to stable26 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable26
git pull origin stable26

# Create the new backport branch
git checkout -b backport/48921/stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 3a39f4a6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/48921/stable26

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Copy link

backportbot bot commented Oct 29, 2024

The backport to stable28 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable28
git pull origin stable28

# Create the new backport branch
git checkout -b backport/48921/stable28

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts, resolve them
git cherry-pick 3a39f4a6

# Push the cherry pick commit to the remote repository and open a pull request
git push origin backport/48921/stable28

Error: No changes found in backport branch


Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews bug
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants