But a force push may be necessary… If you committed an API key you may need to squash history and force push to avoid it being seen in the commit history.
2025-04-02 08:28:16
39
justputthefriesinmybag :
Have a develop branch that needs PR approval into your prod/master branch… or you gonna be putting the fries in the bag
2025-04-02 05:54:51
21
Justin :
Staging is basically for testing your code, why would you take the chance at merging with some stale commit that never made it into master. Force push is correct.
2025-04-24 09:05:29
6
Away On Vacation :
Learn from your mistake as a lead and implement processes/guardrails to prevent stuff you don’t like from happening. No emotion or ego needed.
2025-04-28 17:17:36
4
vince :
No branch protection rules? Lmao
2025-04-23 23:43:18
3
zyr1 :
The sweater explains why its still on your mind 2-3 weeks later
2025-04-30 09:31:24
1
user8186595102501 :
You can set branch protection rules that block force pushes.
2025-04-03 11:11:16
4
Amaan the Data Engineer :
Push straight to prod to save time 👍🏻
2025-04-28 00:16:36
1
Akin | Nutrition App Developer :
Lock it down if you don’t want anyone to force push.
2025-05-10 21:30:56
1
Silhouette Person :
its stagig tho, not prod. chill. also theres github Rules you can do to enforce these types of things
2025-04-07 15:04:45
2
Abydin :
Hello
2025-04-03 10:42:25
1
Abydin :
Please can you accept my friend request
2025-04-03 10:42:39
1
guccibeaniebaby :
Imagine this being your life sigh lol
2025-04-02 11:28:27
2
Chloé ✨ :
😁😁😁
2025-04-06 08:23:09
0
To see more videos from user @kortex.hq, please go to the Tikwm
homepage.