Live data from Hacker News

How to end up with 500k commits in your log

arp242.net

11–20 of 59 posts

Re: How to end up with 500k commits in your log

#11
I have this rails app that behaves really weird on Heroku, where every build fails the first time.

So I have a comment "Commit comment" in my html that I adjust a capitalization on then push again.

Works 100% of the time

I expect to end up in the 500k commits club

Re: How to end up with 500k commits in your log

#13
> And if stuff is awkward then … maybe you’re doing it wrong? No one liked how any of this worked, but just accepted it as a fact of life, like how you would accept that it really sucks that it rains today. That’s an attitude I’ve seen more often and never really understood: if I see something that’s really awkward, frustrating, and time-consuming then I want to fix it, but a lot of people seem happy to just and accept it.

so much this

Re: How to end up with 500k commits in your log

#14
post #4

"A lot of times the concerts weren’t sold out at all, but we pretended it was. It was just a lie. Pretty much 100% of our traffic came in through AdWords, people would search “Something-something concerts tickets”, got an ad from us, and be duped in to buying them at ridiculous prices." Sounds very scummy.

It gets worse > At one point I learned that one company we connected with would literally just invent concerts: they would guess “they’re probably doing a tour next year” and start “pre-selling” tickets for it at extraordinary prices.

Hey now, it's just branch prediction !

Re: How to end up with 500k commits in your log

#15
post #11

I have this rails app that behaves really weird on Heroku, where every build fails the first time. So I have a comment "Commit comment" in my html that I adjust a capitalization on then push again. Works 100% of the time I expect to end up in the 500k commits club

Just use "git commit --amend --allow-empty", no need to change anything!

Edit: this is mixing up two things, what you want in this case is "git commit --amend -C HEAD && git push -f", i.e. replace the current commit with a new hash and force push.

Alternatively you can create an empty commit as above, but that isn't amending.

Re: How to end up with 500k commits in your log

#16
post #12
post #5

It's not hard. I use git add ., git commit -m "asdfghj", git push as my save. Exactly like I press Cmd+S in Photoshop all the time. So naturally I end up with a ridiculous amount of commits.

why bother with a message if it's just garbage?

Because a message is mandatory to be able to make a commit.

Re: How to end up with 500k commits in your log

#18

"A lot of times the concerts weren’t sold out at all, but we pretended it was. It was just a lie. Pretty much 100% of our traffic came in through AdWords, people would search “Something-something concerts tickets”, got an ad from us, and be duped in to buying them at ridiculous prices." Sounds very scummy.

The author agrees “I very much regret working on this First job, insecure about your career prospects and whether you’re able to get a new job, and it becomes easy to rationalize these things to yourself.”

The scam works because they put you under time pressure and the refund laws for internet purchases have an exception for concerts/events. So you think it is almost sold out and you can just get your 2 tickets you want for 200 bucks, you order, afterwards you realize... Wait a minute... There are official sellers... but that's it, you have to pay.

Let's hope karma exists.

Re: How to end up with 500k commits in your log

#20
post #19
post #16

Earlier quoted context omitted.

Because a message is mandatory to be able to make a commit.

Someone above mentioned: git commit --amend --allow-empty

--allow-empty refers to the changeset [1]. You still need a message.

[1] To be precise, it allows to create a commit that has the same tree as the parent commit.

Post reply on HN