@Joshua_1353 sorry about that, I missed it.
As you can see from the flurry of commits I just made to your repository, I'm simply not experiencing the problem. I tried this with both a Secure Credential, and without.
Here's what I discovered during my testing
the Git Raft Editor isn't very clear about "keeping the same password" if it's unchanged, but that's what happens
GitHub doesn't seem to look at the username? I entered invalid usernames and it worked fine
the PAT permission required seems to be "public_repo
Unless you have something that's "doing something" between Otter and GitHub, I think that:
you made a typo or something in your PAT; you can't have any spaces, it must be exactly a PAT, so make sure to edit and save it
your PAT doesn't have right permission
From here, about the onloy thing you could do is attach a proxy server like Fiddler between Otter and GitHub, and see specifically what traffic is flowing through. But like I said I think it's one of the above to