4 ms·

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 adjus

by bgroat 5y ago

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

lambdaba 5y ago
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.
jrochkind1 5y ago
Reminds me of another part of OP: > 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.
- pjerem 5y ago
  I think it’s more like « this place is full of smart people that knows this is shit so if nobody fixed it already, it must be hard to fix ». And since this is a shared behavior, even your potential fix can be hard to get reviewed because everyone will be afraid of the potential side effects because nobody understands why it even worked like this.
pjerem 5y ago
And yet our field is called Software « Engineering ».
breakingcups 5y ago
Seems like an issue on Heroku's end really, maybe some build dependency timeout which is then cached or something. At any rate, I'd either dig in or contact Heroku, I couldn't imagine leaving that lie without knowing the cause. Often, the root cause of this will bite you hardest when you need it least.

4 ms·

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 adjus

by bgroat 5y ago

lambdaba 5y ago
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.
jrochkind1 5y ago
Reminds me of another part of OP: > 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.
- pjerem 5y ago
  I think it’s more like « this place is full of smart people that knows this is shit so if nobody fixed it already, it must be hard to fix ». And since this is a shared behavior, even your potential fix can be hard to get reviewed because everyone will be afraid of the potential side effects because nobody understands why it even worked like this.
pjerem 5y ago
And yet our field is called Software « Engineering ».
breakingcups 5y ago
Seems like an issue on Heroku's end really, maybe some build dependency timeout which is then cached or something. At any rate, I'd either dig in or contact Heroku, I couldn't imagine leaving that lie without knowing the cause. Often, the root cause of this will bite you hardest when you need it least.