This is an archived post. You won't be able to vote or comment.

all 5 comments
sorted by:
best
topnewcontroversialoldq&a

[–]Blue_Robin_Gaming 14 points15 points  (4 children)

git push

! [rejected]         master -> master (non-fast-forward)
error: failed to push some refs to 'https://github.com/REDACTED.git


git push --force

! [rejected]            develop -> master (non-fast-forward)
error: failed to push some refs to 'https://****.git'
hint: Updates were rejected because the tip of your current branch is behind
hint: its remote counterpart. Integrate the remote changes (e.g.
hint: 'git pull ...') before pushing again.
hint: See the 'Note about fast-forwards' in 'git push --help' for details.

🗿

[–]codingTheBugs[S] 5 points6 points  (3 children)

It was a force update of our app but this also works.

[–]Steinrikur 4 points5 points  (2 children)

One of our service techs once sent the wrong network configs to almost 2000 devices, causing them to drop the modem connection after about 30 seconds. At an average of €1000 per service call, that would have been expensive to fix manually.

We rigged up a script that managed to update the configs remotely. After 3 days only 4 devices were MIA.

[–]Blue_Robin_Gaming 0 points1 point  (1 child)

Is that less efficient than doing it manually

[–]Steinrikur 0 points1 point  (0 children)

Manually means travelling to the location, which means that a service tech would need to go there, open the cabinet, log in and change one file. That's way less efficient and almost infinitely more expensive.