ci: Remove “Windows (VS 2022)” task from Cirrus CI #1397

1. 
   hebasto commented at 1:50 pm on August 9, 2023: member

   A follow-up for #1389.

   #1389 (comment):

   Or actually… hebasto Can you remove the second commit for now, if we’re unsure whether this works at all.

   ---

   Second commit effect:

   • before (master branch):

   • after (this PR):

2. ci: Remove "Windows (VS 2022)" task from Cirrus CI 5ee039bb58
3. ci, gha: Make MSVC job presentation more explicit f1774e5ec4
4. real-or-random approved
5. 
   real-or-random commented at 2:15 pm on August 9, 2023: contributor

   utACK f1774e5ec4a49db5762ecccbabd7fb5db0a7fb2b

   Nice, the second commit here clearly shows that the GHA runs its config from the merge commit (and not from master).

6. 
   hebasto commented at 2:25 pm on August 9, 2023: member

   Nice, the second commit here clearly shows that the GHA runs its config from the merge commit (and not from master).

   FWIW, from the “Checkout” step log:

   0"C:\Program Files\Git\bin\git.exe" checkout --progress --force refs/remotes/pull/1397/merge
   

7. real-or-random merged this on Aug 9, 2023
8. real-or-random closed this on Aug 9, 2023

   ---

9. hebasto deleted the branch on Aug 9, 2023
10. real-or-random cross-referenced this on Aug 9, 2023 from issue ci: Future of CI after Cirrus pricing change by real-or-random
11. real-or-random added the label ci on Aug 10, 2023

Contributors
hebasto real-or-random

Labels
ci