ci(psalm): Add missing imagick extension#48921
Conversation
Signed-off-by: provokateurin <kate@provokateurin.de>
provokateurin
requested review from
a team,
Altahrim,
come-nc,
kesselb,
nickvergessen and
skjnldsv
and removed request for
a team
|
@nickvergessen can you force merge? |
|
/backport to stable30 |
|
/backport to stable29 |
|
/backport to stable28 |
|
/backport to stable27 |
|
/backport to stable26 |
|
/backport to stable25 |
|
The backport to # 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/stable27Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # 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/stable29Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # 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/stable25Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # 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/stable26Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
|
The backport to # 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/stable28Error: No changes found in backport branch Learn more about backports at https://docs.nextcloud.com/server/stable/go.php?to=developer-backports. |
3 participants
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