Exclude files from version control (ignore)
Clicking Cancel in the confirmation dialog only cancels force adding ignored files - all other files will be added to the Git repository.
gitignore list, DataSpell will suggest force adding it. If you attempt to add a file that's on the. If you want certain files to always remain unversioned, you can ignore them. You can change this behavior in the Version Control | Confirmation page of the IDE settings Ctrl+Alt+S. When Git integration is enabled in your workspace directory, DataSpell suggests adding each newly created file under Git, even if it was added from outside DataSpell. You can also add files to your local Git repository from the Workspace tool window: select the files you want to add, and press Ctrl+Alt+A or choose Git | Add from the context menu. Select the files you want to add to Git or the entire changelist and press Ctrl+Alt+A or choose Add to VCS from the context menu.
In the Commit tool window Alt+0, expand the Unversioned Files node. If there is no Enable Version Control Integration option available in the VCS Operations Popup, it means that Git version control is already enabled for the project.Īfter you have initialized a Git repository for your project, you need to add project files to the repository. You can choose Always Add to synchronize project settings with other repository users who work with DataSpell. The entire project then will be associated with a single Git directory, so there is no need to add each file to the Git directory individually.Īfter Git integration is enabled, DataSpell will ask you whether you want to share project settings files via Git. Press Alt+` to open the VCS Operations Popup and select Enable Version Control Integration.Īlternatively, from the main menu, select VCS | Enable Version Control Integration.Ĭhoose Git as the version control system and click OK. Open the workspace directory that you want to put under Git. Associate the workspace directory with a Git repository You can create a local Git repository based on the existing project sources. Put an existing project under Git version control If your project contains submodules, they will also be cloned and automatically registered as project roots. Git root mapping will be automatically set to the project root directory. If you want to create a project based on the sources you have cloned, click Yes in the confirmation dialog. If you are already logged in to the selected hosting service, completion will suggest the list of available repositories that you can clone.Ĭlick Clone. In the Get from Version Control dialog, specify the URL of the remote repository you want to clone, or select one of the VCS hosting services on the left.
Check out a project from a remote host (clone)ĭataSpell allows you to check out (in Git terms clone) an existing repository and create a new project based on the data you've downloaded.įrom the main menu, select Git | Clone, or, if no project is currently opened, click Get from VCS on the Welcome screen. If you need to manually configure DataSpell to use Git from WSL, go to the Version Control | Git page of the IDE settings Ctrl+Alt+S, click the Browse icon in the Path to Git executable field and select Git from WSL via the \wsl$ path, for example, \\wsl$\debian\usr\bin\git. Also, DataSpell automatically switches to Git from WSL for projects that are opened when you use the \\wsl$ path. If Git is not installed on Windows, DataSpell searches for Git in WSL and uses it from there.
#Dataspell cost windows 10#
If the IDE can't locate a Git executable, it suggests downloading it.ĭataSpell supports Git from the Windows Subsystem for Linux 2 (WSL2), which is available in Windows 10 version 2004. When you clone an existing Git repository, or put an existing project under Git version control, DataSpell automatically detects if Git is installed on your computer.
0 kommentar(er)
