Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,554,456
Community Members
 
Community Events
184
Community Groups

Last 10 days of work is lost after git push --force

Edited

I tried to add pattern to GIT LFS today and all the work in the last 10 days are gone!!! The last commit seen is 11th Nov. All the work in between are all gone!!!

Last week I added *.html to GIT LFS. Today I tried to add *.{html, svg} and this is what I get!

GITLFSProblem.png

$ g reflog show --all
a7406c404 (HEAD -> UpgradeDotNetCore, origin/UpgradeDotNetCore) refs/remotes/origin/UpgradeDotNetCore@{0}: update by push
a7406c404 (HEAD -> UpgradeDotNetCore, origin/UpgradeDotNetCore) refs/heads/UpgradeDotNetCore@{0}: commit: Fix GIT
a7406c404 (HEAD -> UpgradeDotNetCore, origin/UpgradeDotNetCore) HEAD@{0}: commit: Fix GIT
1eaf71063 refs/remotes/origin/UpgradeDotNetCore@{1}: update by push
1eaf71063 refs/heads/UpgradeDotNetCore@{1}: commit: Track wwwroot
1eaf71063 HEAD@{1}: commit: Track wwwroot
207186a6c refs/heads/UpgradeDotNetCore@{2}: branch: Created from refs/remotes/origin/UpgradeDotNetCore
207186a6c HEAD@{2}: checkout: moving from dev to UpgradeDotNetCore
be3b63495 (origin/dev, origin/HEAD, dev) refs/heads/dev@{0}: clone: from https://kokhow@bitbucket.org/4xlabs/bz-frontend.git
be3b63495 (origin/dev, origin/HEAD, dev) refs/remotes/origin/HEAD@{0}: clone: from https://kokhow@bitbucket.org/4xlabs/bz-frontend.git
be3b63495 (origin/dev, origin/HEAD, dev) HEAD@{3}: clone: from https://kokhow@bitbucket.org/4xlabs/bz-frontend.git

Any advice and insight is appreciated.

1 answer

0 votes
Ana Retamal
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Nov 25, 2019

Hi @kokhow.teh ,

Thanks for reaching out!

This is not an issue with Sourcetree or Bitbucket, this is how Git works. The good thing about Git is that it is a version control system, so your work is not lost, you just need to go back to a previous version before you did the force push and you'll be able to continue working from that point on.

You can learn different ways of undoing changes in one of our tutorials. You can also refer to the official Git documentation for further explanation.

Hope that helps,

Ana 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events