[3.11] gh-76773: Update docs mentioning no-longer-supported Windows versions & features (GH-92529)#92608
Conversation
…rsions & features (pythonGH-92529) (cherry picked from commit f1bbcba) Co-authored-by: CAM Gerlach <CAM.Gerlach@Gerlach.CAM>
|
@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ . |
|
@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ . |
1 similar comment
|
@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ . |
|
@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ . |
1 similar comment
|
@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ . |
|
@CAM-Gerlach and @serhiy-storchaka: Status check is done, and it's a success ✅ . |
|
Is there a reason @miss-islington has to spam the backport, and our notifications, with a stream of identical comments just stating the status check was a success over and over? Can it only comment once if the status check failed, and edit its comment if that changes, like other bots do? |
|
Sorry, I can't merge this PR. Reason: |
|
@miss-islington: Status check is done, and it's a success ✅ . |
1 similar comment
|
@miss-islington: Status check is done, and it's a success ✅ . |
|
Sorry, I can't merge this PR. Reason: |
|
@miss-islington: Status check is done, and it's a success ✅ . |
1 similar comment
|
@miss-islington: Status check is done, and it's a success ✅ . |
|
Sorry, I can't merge this PR. Reason: |
2 similar comments
|
Sorry, I can't merge this PR. Reason: |
|
Sorry, I can't merge this PR. Reason: |
|
@miss-islington: Status check is done, and it's a success ✅ . |
(cherry picked from commit f1bbcba)
Co-authored-by: CAM Gerlach CAM.Gerlach@Gerlach.CAM
Automerge-Triggered-By: GH:serhiy-storchaka