What needs to be checked before anything else is the access level, which should be set to write. This can happen if you were added to the repo by someone else, and they forgot to grant you the required permissions.
Glad you corrected the issue. I recently ran into the same issue. It a merge conflict and that is why Xcode is throwing that error. Within the .xib file you will see something like: <<<<<<< HEAD // code ======= // code >>>>>>> apps You can do what you did above, or manually correct the merge … Read more
The question has wrong terminology. You cannot pull a commit, you can only checkout a commit. Pulling a commit would defy the whole branch/commit structure saving memory. You pull all commits in a branch or repository, and if you want to check out a specific one, then well, check it out: git checkout 9ce920d You … Read more
The url below should work. Just change required parts. https://bitbucket.org/<username>/<reponame>/get/<commitCODE>.tar.gz (without hypens)
A Mercurial repository gets its identity when you make the first commit in it. When you create a new repository on Bitbucket, you create an empty repository with no identity. When you clone this repository to machine A and make a commit and push it back, then you brand the repository. If you have cloned … Read more
I had a similar situation. Though it was due to me having the solution open in visual studio. Closing visual studio and doing a git reset put me into a good spot. I.e. check to see if any processes are locking the folder/files.
First, make sure you already installed EGit or other git control plugins on your Eclipse. Second, add Git Source Control to your existing Android Eclipse Project (local) and create a local Git Repository for the Project, by following the steps below: (or check this video) right click your project -> Team -> share project check … Read more
I just disabled SSL certificate checks (which is fine for internal repos): Sourcetree > Preferences > Git > Disable SSL certificate validation (ticked)
Putting this in my .hgrc did the trick. [hostfingerprints] bitbucket.org = 45:ad:ae:1a:cf:0e:73:47:06:07:e0:88:f5:cc:10:e5:fa:1c:f7:99 You should check the fingerprint first by viewing the host’s certificate. But if all looks fine you could use the above approach to do away with those pesky warnings. See https://confluence.atlassian.com/display/BBKB/abort%3A+certificate+for+bitbucket.org+has+unexpected+fingerprint
I’ve found that the easiest way to reduce the Bitbucket repo size if you are over the 2GB limit is to Create a branch on Bitbucket Delete that branch on Bitbucket This should trigger Bitbucket to run git gc on the repo.