![]() So I did an git init then tried a git push master, which gave me two new errors: fatal: 'master' does not appear to be a git repository and fatal: Could not read from remote repository. That struck me as odd since I had definitely been able to push updates from this repo in the past. If I add or modify a file in the folder its reading from, then stage, commit, and push the changes, when I go to the relevant section on my GitHub I can see that the changes haven't been applied.Įdit 2: So I cd to where the repo is stored, and when I typed git push I got the message fatal: not a git repository. ![]() Here's a screenshot of my GitKraken setup if that helps.Īfter I click the Push button it spins for a while then gives me the message "Pushed Successfully: main to origin". Am I missing something? I've set Upstream to origin/master, I've tried making a new branch and then merging it. GitKraken is telling me that the push is going through but I'm not seeing any file changes on. I'm on gitkraken where I've added several files to the local repository, and I'm trying to push them to my remote repository on, so that I can use them for a website. To learn more about oclif, you can visit their website.I'm really new to anything git-related so hopefully this question isn't too obvious. ![]() After changing this to your non root user gitkraken is able to watch your files. My problem was that in ubuntu 20.04 the folder with my repositorys the owner/group was root. Migrating Salesforce CLI to oclif will not change the way you interact with the CLI, and the force commands will work as they did before. However, Salesforce CLI will NOT be backwards compatible with plug-ins built on the original CLI engine. If the plug-in was created using Salesforce Plug-In Generator (sfdx plugins:generate), it will still work, because the generator already uses oclif. If you have the problem that gitkraken cannot watch the files you should check the owner en permissions in the wsl directory. We expect this change to improve the performance and reliability of Salesforce CLI and to help us add new functionality more quickly. We plan to release our next update, v45.8.x of the salesforcedx aggregate plug-in and and v7.x.x of sfdx-cli, on Thursday, March 28, 2019. To allow time for testing and to facilitate a smooth transition, we will not be releasing updates for the next 3 weeks. This migration is a major update for Salesforce CLI and our core plug-ins. We are migrating the cli-engine framework over to Heroku's Open CLI Framework (oclif) in the coming weeks. The "good" version will be released soon. day (ideally) because that changes all the time and that tool is still very unstable (many bugs). ! autoupdate:: C:\Users\ \AppData\Local\sfdx\ update.lock is locked with an active writerĪnd we need to upgrade sdfx every. Warning: sfdx update is very slow and you will need to delete the update.lock (otherwise that will never work) The VS Code/sfdx constraint is unbearable for the development of LWC components (that never works as expected) until recently.Ĭ:\sfdx> sfdx plugins:uninstall salesforcedxĬ:\sfdx> sfdx plugins 1.0.1 2.0.1 (core) ![]() Ideally, the developer console should support the development of LWC directly like the Aura lightning (stable). Christophe Coenraets (French) published warnings for sfdx bugs until recently and Zayne Turner only uses copy/paste of the command lines for SFDX. My 'TypeError: Cannot read property muiName of undefined' is caused by variant attribute. René Winkelmeyer (German) is the main Evangelist for VS Code. Now there are two options: sfdx command lines (that never works as expected) and the (old) unmanaged package as usual (that always works fine). The first LWC apps were published with warnings for the "bugs" each time at the begining and that is the REFERENCE applications: We often struggle with the commands of upgrade for the sfdx cli itself as I have written above (there are interferences with node, npm, the direct exe installation, and so on, big mess even if you uninstall an reinstall everything, that is not so simple, waste of time). This package.xml file was generated by VS Code extension. The development environment is Salesforce Spring 2019 Sfdx force:source:retrieve -manifest c:\_hilton\BossReno\manifest\package.xml Here is the command that is being issued in VS Code when I click on the package.xml file and retrive source from org: GitKraken We make a suite of legendary Git tools that help developers be more productive and teams collaborate more closely wherever they are and wherever they code. ![]() I am getting an error when trying to do a sfdx retrieve:ĮRROR: Cannot read property 'fileName' of undefined. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |