… and prefer ssh if possible (#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

* master: (447 commits)
  chore(Data/Set): move very basic lemmas earlier (leanprover-community#25707)
  feat: preserve draft status when migrating PRs to fork (leanprover-community#25777)
  chore(Data/Set/Basic): deprecate lemmas that abuse the `Set α := α → Prop` defeq (leanprover-community#25669)
  refactor: redefine `ProperCone` as an `abbrev` for `ClosedSubmodule` (leanprover-community#25204)
  feat: interaction between ContinuousLinearMap.coprod and ContinuousLinearEquiv.prodComm (leanprover-community#25564)
  fix: outdated docstring (leanprover-community#25717)
  feat(MeasureTheory): convolution of measures with densities  (leanprover-community#25718)
  feat: make sure that the simp normal form of equiv-like classes pushes `symm` and `trans` to the right (leanprover-community#25604)
  feat(ModelTheory): Formula.iSup and iInf (leanprover-community#21948)
  feat(RingTheory/Polynomial/ContentIdeal): the content ideal of a polynomial. (leanprover-community#25333)
  fix: typo in labels_from_comment.yml (leanprover-community#25727)
  feat: is{Inducing,Embedding}_prodMkLeft (leanprover-community#25705)
  feat: check that the mathlib options exist (leanprover-community#25687)
  feat(Algebra/Group/Even): Add missing lemmas (leanprover-community#20818)
  refactor: make `Matrix.kroneckerTMulAlgEquiv` heterogeneous (leanprover-community#25693)
  feat: allow contributors to remove labels with comments (leanprover-community#25723)
  chore: disable build.yml and bors.yml on forks (leanprover-community#25722)
  feat: improvements to user_activity_report.py (leanprover-community#25721)
  chore: update the migration script to check for necessary permissions and prefer ssh if possible (leanprover-community#25701)
  chore: update the migration script to check for necessary permissions and prefer ssh if possible (leanprover-community#25701)
  ...

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>

… and prefer ssh if possible (leanprover-community#25701)

The sync step requires the gh token to have particular scopes which don't seem standard. So we now check for them and bail if not there. We also check for successfull ssh access to GitHub and use ssh as the protocol for the remote in this case falling back to https.



Co-authored-by: Kim Morrison <kim@tqft.net>