@aescling the merge must have changed the CI setup, which if we used CI would have modified our workflow
we DON'T use CI but upstream does so the workflow is there even though it is inactive
@aescling we could get rid of this but it would mean a merge conflict every time upstream updated their settings
@Lady we merge rarely enough that i’d be fine with that
i didn't even mention the whole deal with forgetting my login credentials to github (which was necessary to push the merge commit branch, because for some reason, i needed an access token with workflow priveleges)