Matt Olson

@noamd-legit +1 for this - this is a blocker from a client being able to use this product because they aren't comfortable with using a PAT token in this instance.

@noamd-legit - I did a bunch of digging into Legitify's source code, and I think I see why this isn't an "easy fix" scenario, and instead would require a pretty...

Hey @noamd-legit - thanks for reaching out. I agree, it would be nice if they distinguished between a "you can't do that" (a 401) versus "you're not allowed to do...

The classic PAT requirement is in the documentation - https://docs.github.com/en/enterprise-cloud@latest/migrations/using-github-enterprise-importer/migrating-from-azure-devops-to-github-enterprise-cloud/managing-access-for-a-migration-from-azure-devops#creating-a-personal-access-token-for-github I suspect this is due to Fine-Grained PATs (and apps) not having support built in for all permissions yet (for...

Referencing this issue here - #10781 is caused by this. Documentation should be updated to reflect this breaking change, or the interpreter of python that comes with the runner image...

Hey @ArinGhazarian - thanks for the response. That makes sense, the migration logs aren't actually tied to the migrated repo (they're stored separately). Is that something that can be changed,...