You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I've forked one of my repositories and I now want fork it's LFS as well.
Following this guide:
I've got to the point of
git lfs push --all origin
And I got
batch request: Unauthorized: exit status 1
I've tried adding an SSH key, I've made sure that I have read, write and even admin permissions. all to no avail.
Steps to reproduce:
Create a repo, install LFS, track a file using LFS, Fork the repo and follow above guide.
Hello @Kostya Sydoruk ,
Welcome to Atlassian Community!
I tried to reproduce the error you reported and the LFS push was completed successfully, so let me share the steps I've followed with you :
1. Clone the main repository in my local
2. Fetch all LFS history
git lfs fetch --all origin
At this point, your local clone should have all the LFS files downloaded
3. Inside the local clone, add a remote that points to the forked repository :
If using SSH :git remote add fork-origin email@example.com:<fork's workspace>/<fork repository>.git
Make sure the SSH key being used is associated with a user that has write access to the forked repository.
If using HTTPS :git remote add fork-origin https://BITBUCKET_USERNAME@bitbucket.org/<fork's workspace>/<fork repo>.git
When using HTTPS, if asked for a password, make sure to provide an App Password with the required permissions. If you are still getting an Unauthorized error, you can create an App Password with all permissions checked and try again.
4. Push the LFS files to the forked repo using the origin you set in Step 3 :
git lfs push --all fork-origin
You can try following the steps above and let us know how it goes.
Thank you, @Kostya Sydoruk .