134
balte
4y

today the inevitable finally happened.. I put my password in the code and committed to github.

Comments
  • 5
    Congratulation! 😂
  • 4
    now you have to delete the repo.. Or change your pass.
  • 10
    @romangraef change password.

    Even if it is deleted someone might already have seen it. :/
  • 8
    Change your password, then reset the commit and force push (not that it's really necessary)
  • 4
    At least you caught it
    Some people never realize they have done it.
  • 2
    Did somebody ask for bleach?
  • 0
    @YeahOkay handle?
  • 1
    @vhoyer a handle is kinda like a username
  • 1
    @romangraef oh, thanks
  • 1
    @YeahOkay ooooh have you been spying around?
  • 3
    @balte we all do (i hope at least). would be unprofessional if we'd skip the background checks.
  • 2
    It has happened to me before. You can use git filter-branch to fix it instead of deleting your repo or creating a new one.

    See https://help.github.com/articles/...
  • 1
    Been there, did that..

    Even though you force push, anyone can still see the file history (or maybe I did something wrong) I had no choice but to delete / recreate the repo 😅😅
  • 0
    @TwiN if I recall if someone had the hash they can find it still.
  • 0
    @demortes locally sure but why would github keep track of orphaned commits?
  • 0
    @Commodore I assume it's like Gmail. Archive everything. Probably can be told to clean it up through repo settings though so maybe they don't? I'd have to test.
  • 0
    How do you even come to do that?
  • 1
    @Cyanide email connection: bootstrapped using my own email account while my request for a dedicated account was still pending.
  • 3
    @balte I didn't understand a word you said. But I'll buy it.
  • 3
    Email me with the same email address you use for github and I'll fix it for you :d
Add Comment