From: Jeffrey Barish <jeffbarish73@gmail.com>
To: git@vger.kernel.org
Subject: Bug
Date: Thu, 18 Jul 2024 13:10:54 -0600 [thread overview]
Message-ID: <CAKjFfK_vcD-36LqYDMfEEjMARGQKFMQbKH7GqUPzrEjU-_HuQw@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 19 bytes --]
--
Jeffrey Barish
[-- Attachment #1.2: Type: text/html, Size: 217 bytes --]
[-- Attachment #2: git-bugreport-2024-07-18-1259.txt --]
[-- Type: text/plain, Size: 1431 bytes --]
Thank you for filling out a Git bug report!
Please answer the following questions to help us understand your issue.
What did you do before the bug happened? (Steps to reproduce your issue)
I did:
<create a new repository>
git init
git add .
git commit -m "Initial commit"
git remote add origin https://github.com/jeffbarish/wax
git push -u origin master
What did you expect to happen? (Expected behavior)
I expected my files to get pushed to my repository.
What happened instead? (Actual behavior)
I got a popup window demanding a password for a username that appears to be a random string of characters.
What's different between what you expected and what actually happened?
The files should be transferred, or, at worst, I should get a request for a password for username jeffbarish
Anything else you want to add:
I am prepared to delete my account and start over, but I do not see a way to do that. In any case, I wonder whether there is a better solution.
Please review the rest of the bug report below.
You can delete any lines you don't wish to share.
[System Info]
git version:
git version 2.43.0
cpu: x86_64
no commit associated with this build
sizeof-long: 8
sizeof-size_t: 8
shell-path: /bin/sh
uname: Linux 6.8.0-38-generic #38-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 7 15:25:01 UTC 2024 x86_64
compiler info: gnuc: 13.2
libc info: glibc: 2.39
$SHELL (typically, interactive shell): /bin/bash
[Enabled Hooks]
next reply other threads:[~2024-07-18 19:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-18 19:10 Jeffrey Barish [this message]
2024-07-18 21:34 ` Bug brian m. carlson
-- strict thread matches above, loose matches on Subject: below --
2020-11-04 16:10 BUG Alex Marginean
2020-11-04 17:02 ` BUG Randall S. Becker
2020-11-04 17:54 ` BUG Randall S. Becker
2020-06-26 21:11 bug Luke Knoble
2016-09-13 17:18 Bug Mike Hawes
2016-09-13 17:26 ` Bug Santiago Torres
2016-09-14 22:14 ` Bug Dennis Kaarsemaker
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKjFfK_vcD-36LqYDMfEEjMARGQKFMQbKH7GqUPzrEjU-_HuQw@mail.gmail.com \
--to=jeffbarish73@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).