sketchy fix for leaking usernames #11

Open
sebastianbl wants to merge 1 commit from sebastianbl/2026-latam-git:leaking_valid_usernames_fix into main
Member

not a solution but a temporary fix, works only with sys.arg[1]

not a solution but a temporary fix, works only with sys.arg[1]
This pull request has changes conflicting with the target branch.
  • auth.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u leaking_valid_usernames_fix:sebastianbl-leaking_valid_usernames_fix
git switch sebastianbl-leaking_valid_usernames_fix

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff sebastianbl-leaking_valid_usernames_fix
git switch sebastianbl-leaking_valid_usernames_fix
git rebase main
git switch main
git merge --ff-only sebastianbl-leaking_valid_usernames_fix
git switch sebastianbl-leaking_valid_usernames_fix
git rebase main
git switch main
git merge --no-ff sebastianbl-leaking_valid_usernames_fix
git switch main
git merge --squash sebastianbl-leaking_valid_usernames_fix
git switch main
git merge --ff-only sebastianbl-leaking_valid_usernames_fix
git switch main
git merge sebastianbl-leaking_valid_usernames_fix
git push origin main
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ASPP/2026-latam-git!11
No description provided.