To begin with, a few clarifications: 1. I work in PHPStorm 2. in https://bitbucket.org/ I keep projects in git format 3. bitbucket.org producer provides a tool called Sourcetree to handle these projects graphically - something like "Git gui", only 100x more powerful
>From the very beginning I set up a project in https://bitbucket.org/, in >PHPStorm I point to the path to the project online (commit, etc. done directly >from PHPStorm) - in Sourcetree I browse commits and the repository, because it >is more clearly shown there - I don't actually perform operations in this >tool. It is used for browsing. Everything worked - in PHPStorm I wrote code and approved changes. The code was saved locally and to bitbucket.org, where I could view it either via the Web or using Sourcetree. I worked on several projects this way. After upgrading to 2.38.1, both in the project where I "cleaned everything up and set up a repository from scratch" and in others (where I did not make rare changes the same problem appeared - with code 128. That is, even if I set up a repository from scratch, it still does not work. I never used git directly -> I didn't need it for anything. Therefore, I don't even really know what and how to check in order to give the answers you are waiting for. I am looking on the web - there is no version 2.39 anywhere - where to download it? Maybe it is better to go back to some older version (only this way I will not escape the problem - only postpone it). -----Original Message----- From: git-users@googlegroups.com <git-users@googlegroups.com> On Behalf Of Konstantin Khomoutov Sent: Saturday, December 3, 2022 1:54 PM To: git-users@googlegroups.com Subject: Re: [git-users] Re: The git projects disappeared after the updated On Sat, Dec 03, 2022 at 09:24:31AM +0100, rozanski.s...@gmail.com wrote: > I am convinced that something serious has changed in the new version of git. > > I could afford it, so in one project I deleted the repository in > Bitbucket and set up a new one (renamed). Then I removed the .git from > the project directory and cloned the project to where the old one was. I thought Bitbucket is a Git reposiory hosting solution, but your message sounds as if Bitbucket is a desktop application. Am I correct, and such application does really exist and you have used it to clone a Git repo? > In the SourceTree application, everything worked fine - I ran PHPStorm > and got a message that there was no git repository, or the root > directory was not set. In PHPStorm, I set the root directory of the > project, as "commit directory", and since then, in the SourceTree app, I got > the message: (Please do not post screenshots of text - I'll give a short explanation as to why, after the bulk of my message). > Interestingly - in other projects, where I didn't change anything, in > the SourceTree app I have exactly the same error message with code 128. I don't quite parse this part about SourceTree and PHPStorm. I read it as follows: 1. SourceTree worked fine on a particular repository (cloned using Bitbucket?). 2. You have tweaked some setting in PHPStorm trying to "attach" it to that repository, and... 3. ...that made SourceTree fail on that repository - saying it's unable to run `git status` there and exiting with exit code 128. 4. With all other existing (not re-cloned from somewhere using Bitbucket) Git repositories SourceTree behaves exactly as described on step 3. Is the above correct? > Something has changed between the new version of git and PHPStorm - > just what? While your investigation is interesting, I would again urge you to listen what I and Philip have suggested and verify whether _plain Git works_ (or doesn't). To understand my insistence, you should consider two facts: * Git is not only a piece of software but also a documented format of the repository which actually holds the data and protocols Git clients and servers use to exchange data between different Git repositories. * While Git-as-a-software-package does provide low-level command-line tools specifically tailored to be called by other pieces of software, no piece of software is oblidged to do so - exactly because the format of Git repositories and the Git data exchange protocols are documented, and any programmer can implement a piece of software which works with Git repositories and communicates using Git data exchange protocol. So, you've basically tested three pieces of software - Bitbucket (I have no idea what it is, but let's assume it's really a piece of software), SourceTree (I've managed to google it) and PHPStorm, and neither of them is a part of Git, and I have no idea whether they actually call out to Git to carry out their Git-related tasks or implement some other ways to work with Git repositories). Because of that, we cannot guess what actually broke because you did not yet try to actually run _Git itself_ and see if it works. If we'll see plain Git fails, that will be one path to follow further, if we'll see plain Git works but the software using it fails, then that's a hint something has changed in Git in a way which broke those pieces of software. And while we're at it - may by try installing 2.39.0? It has been released [*]. --- A note on screenshots of text. There are multiple problems with them: - They assume whatever way the mail readers use to read their mail readily and conveniently shows embedded image attachments. Good or bad, but as e-mail was invented for text, and is primarily about text, quite many dinosaurs like me read it using console-based software - even though this software runs in an otherwise graphical desktop environment. - Text in images is not indexed by Internet search engines. I mean, the error shown by SourceTree may be the key to the problem, but even though our e-mail exchange is archived and indexed by Google, that error message is not - because it has never been written in any of the mail messages in this exchange in the text form. Hence our discussion is impossible to find on the Internet using the key words. I mean, the next guy to have this problem will type that error message in their browser and the Internet search engine of their choice will be unable to find our discussion. Please note that consoles on Windows have an ability to select and copy text displayed in them, and even the apparenly GUI-only windows such as standard Windows dialog boxes support pressing Ctrl-C in them to copy the text they display to the clipboard. More explanations - here [**]. [*] https://groups.google.com/g/git-for-windows/c/mHKYD4XZ4o0 [**] https://meta.stackoverflow.com/a/285557/720999 -- You received this message because you are subscribed to a topic in the Google Groups "Git for human beings" group. To unsubscribe from this topic, visit https://groups.google.com/d/topic/git-users/lD2ekpYaKF4/unsubscribe. To unsubscribe from this group and all its topics, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/20221203125341.57wppgf24p4zg6qr%40carbon. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/003801d90742%24da7a62b0%248f6f2810%24%40gmail.com.
