There is a .git folder inside my template database that wasn't there before AFAIK. It must have happened when I clicked Sync with On-Disk Project recently, but I really don't know exactly when or why.
It's rather annoying, because handling this folder can take quite some time when I compile the application.
Do I need this folder inside the database, and if not, how can I get rid of it, i.e. remove it from the database?
The .git folder and its content is of no use inside your database. The problem arises because the on-disk content of your database is at the same level as the .git folder. The .git folder is therefore imported into your database when you sync with the on-disk project.
You should move the on-disk content of your database to a sub folder of your Git folder.
Here's an example of the folder structure (using the OpenNTF Domino API Demo Database):
Related
where can I find .git folder to delete a repo on my system. I opened my local disk as a repository and I have about 5k changes to make.The thing is if I check my git account my local disk is not showing as a repo so i really dont know what is going on. Any solution will be welcomed.
Among the "5k changes", select a file and open it in your file browser. Enable hidden files/folders. Start moving up the hierarchy of that path, i.e., keeping going up in the parent directory of the file.
You'll find the .git folder somewhere. Check its creation date. If it's recent, delete it. Be careful not to delete any commits you had made in some project.
After selecting Initialize Repo on a particular folder and letting VSCode do its thing, I realized I had a number of items in the folder that I didn't want Repo'd. Rather than move those items out of the folder, however, what I want to do is create a new folder for the stuff I do want repo'd and initialize that.
How do I go about 'uninitializing' the current folder so that it isn't tracked anymore?
When you create a git repository, a hidden ".git" folder is created in the repository folder. If you want to "uninitialize" it, you just have to delete it.
I am trying to check out multiple items from two repositories. One checkout goes to the root folder, and another would be checked out to a subdirectory.
Structure:
root
source
invoice.p
compiled
invoice.r
forms
templates
invoice01.xml
invoice01.png
I right-click on the root folder and click "SVN Checkout...". I'm checking out the invoice.p and invoice.r files (specifically) with the same structure from the first repository. The checkout type defaults to "Custom Depths" and everything goes fine. The source and compiled folders show up with the check icon. Then I'm trying to get the invoice files from the second repository, but I am not sure how to check them out. I can right-click on the forms folder in my checkout directory, but no matter how I set it up, it always pulls down the wrong structure, for example:
forms
templates
forms
templates
invoice01.xml
invoice01.png
If I try to select the root folder to check out from the second repository, the original source and compiled folders get overwritten/deleted since they don't exist in the second repo. I can choose invoice01.xml and invoice01.png to go to the templates folder one at a time, but for some projects I may have 30-40 items I'd need to individually check out. Is there an easier way to check out multiple items but to ignore the folder structure?
You can't nest working copies (which is what you're attempting to do here). The lone exception is if your inner working copy is created via an svn:external pointing elsewhere.
If you create an svn:external in the repository directory root is pointing at, call it forms and point it at the URL for the forms repository, you can do what you're attempting. Otherwise, it's not possible.
To answer your query, in case the files are in the same root location like:
-forms
-templates
- invoice01.xml
- invoice01.png
They shall be checked out with the Tortoise SVN URL Repository paths separated by * (asterisk symbol) like:
forms/templates/invoice01.xml*forms/templates/invoice01.png
Thus, in one go only, these files inside the root folder would be checked out even if the actual folder of templates had other files.
In case of a different root location, different folders have to be created and checked out. No other way!
I am creating a new meteor app and would like to put the whole thing under git source control. When cloning a working copy of my meteor directory, meteor gives : run: You're not in a Meteor project directory.
After inspecting the .meteor directory, I see that the files in here are being excluded in my local clone.
Is there a particular reason this is done?
as #Swadq already pointed about, the .meteor directory is Meteor's directory. It contains a folder and a file.
The local directory contains the compiled version of your application and some database information (lock-file and the actual raw data of mongodb). This of course should not be included in your VCS.
The package file contains all packages meteor should load for your application. This is of course important and must be included in your VCS. More importantly: this file is checked for to determine if the current directory is a meteor application. If you don't include this you'll loose the packages you relay on and the ability to simply run the app. using meteor.
So ideally your .gitignore file only should contain .meteor\local but not .meteor\packages. When using meteorite the .gitignore file should contain .meteor\meteorite as well.
I am working with a CVS repository found on a remote server.
I check out the code to a local directory code_local
Then I copy code_local, into code_local_2
Do I have now two independent local copies of the repository? Can I change files, commit, update etc. on each directory independently, is if it was done form two different computers?
(this may depend on the way CVS stores information about a local copy)
Yes I do know it's not a straight forward use of CVS, just asking if it will work
Do I have now two independent local copies of the repository?
Yes you have two independent LOCAL copies.
Can I change files, commit, update etc. on each directory
independently?
No, both copies point to the same file on the same repository. so they are independent as long as you haven't committed them. when committed the last commit operation will overwrite the previous one.
in fact there is a CVS folder beside every folder of your code that keep repository information of files inside that folder. so when you copy a project or a package, the CVS folder will be copied along with, so the same repository entries will be referenced, no matter how many copies have you made.
Even if you past the copied folder to another package hierarchy, whenever you commit the files it will replace the original files in repository where it first created.
If you want to have independent copies you have to copy and place your source code (.java) files only and commit it through Eclipse for example, in this case the CVS plug-in doesn't find any existing CVS folder beside the new folder and generates a new one in the local and new entries in the repository.