I see an inetresting package and I want to play around with it. Should I create a layer and then create an extension folder and in that folder I git clone the package ?
The default folder after I run create layer doesnt have the extension folder.
What is correct workflow for my situation?
Related
I am looking to do something I thought was pretty simple... I have an existing folder (with project files) on my desktop that I would like have tracked by Github desktop for purposes of source/version control. It seems straightforward... I go to github desktop, select that I'd like to create a new repository, and point it at the folder on the desktop. Here is what I expect to happen:
Desktop
Project folder
Project files
(hidden) .git folder
(hidden) .gitattributes
Instead, this is what I get:
Desktop
Project folder
Project files
New folder with specified git repo name
(hidden) .git folder
(hidden) .gitattributes
I am not sure why this is happening and it is very frustrating. It looks to me like I have only two options here:
Cut and paste Project files into New folder with specified git repo name
Cut and paste .git folder and .gitattributes out of New folder with specified git repo name and into Project folder, delete New folder with specified git repo name, remove the new repo in Github Desktop when it says it can't find it, and "Add Existing repo" in Github Desktop and point it at Project folder.
Both of these approaches sort of feel like hacks and I am not sure what consequences, if any, may negatively impact my version control intention as a result. Is this a common problem? What should I do?
I wouldn't use github desktop to make your repository. If you don't have it already try installing git bash, a command line interface, and initialize git from there.
Find your existing folder and move to it using cd <folder name here> if you go into the wrong place use cd .. to move out/back one folder
When in your folder use git init to initialize git(the version control software)
Open GitHub Desktop once again and hit "add" then "add existing repository" finally "choose" and find your file in your file explorer
When you go to "Create a new repository":
Name: New folder with specified git repo name
Local Path: Desktop (ie one level up from Project files)
This will create the .git and .gitattributes in your existing folder without affecting the other files.
The Create a new repository dialogue seems to assume the name should be used as a new folder under the path you specify.
Note that if there are spaces in your name, it tries to replace them with hyphens.
When I create Xcode workspace project and added Swift Package and wrapper project to test Swift Package it all works fine. But when I try to pull this repo from other projects using git url it complains about Package.swift(manifest) file is not present in the Root folder. Is there any solution for this. Do I have to manually drag the Package.swift file to root folder and change the path settings in it?
when I had empty git repo created, instead of creating new Swift package inside the repo which created extra project folder with Package.swfit inside it, I just ran "swift package init --type library" inside the repo so that package.swift is created in the Root folder and takes the repo name as the package name. we can also change the package name if we want to.
Git Repo
iOS-NewRepo ->
Package.swift
Sources
Tets
So I have a git repository for a few related Java classes with a folder structure similar to this:
mylib/LICENSE
mylib/README
mylib/src/file1.java
mylib/src/file2.java
mylib/test/tester.java
...
Now, I'm creating an Android app in Eclipse with the traditional folder structure like:
repo/AndroidManifest.xml
repo/bin/*****
repo/res/*****
repo/src/com/mysite/project/activity1.java
...
Now, I'd like to add the java classes to my android project in the folder:
repo/src/com/mysite/mylib/file1.java
However, if I add it as a git submodule, they are saved to the path:
repo/src/com/mysite/mylib/src/file1.java
Also, included is the tester.java, and some other files I don't want in the Android project.
What is the best way to resolve this? Should I just leave the path as com/mysite/mylib/src/file1.java? Or should I modify the repo and move the files from mylib/src up into mylib and delete the files I don't want?
The simplest way would be to:
keep your original (non-Android) repo separate
add that original repo 'src' folder as a source folder of your Android Eclipse project (an Eclipse project can defined several src folders, from various origin)
That will sidestep the "submodule" issue entirely, and allow you to select from your original project only the files you need for your Eclipse Android project.
Current scenario :
In Eclipse when we create a project, say a PyDev project named ‘SimpleGit’, the folder structure created by eclipse will be like
EclipseWorkingDirectory/SimpleGit/src/
correct?
If we add this to git using Egit, by right clicking on the project folder SimpleGit then Team>Share, The folder structure in which repo is formed like this
Parent Folder/ SimpleGit/ .git
Parent Folder/ SimpleGit/SimpleGit/src/
And when we stage it to remote github everything will come under
Username/ SimpleGit / SimpleGit / src /
So when we look in GitHub in the root project folder (Username/ SimpleGit) we can’t see the source folder. It will be under another folder ‘SimpleGit’. How we can avoid this?
What I want is , I want to get my source forlder(src) listed under the Project Root directory, when staging from an already built project in eclipse using egit. How do I do this?
I want like this:
https://github.com/nicholasbishop/blender
Not like this:
https://github.com/afilash/SimpleGit
it cannot be done using eGit - it assumes the Eclipse project structure.
But it can be accomplished by using git itself. Just create a repository under SimpleGit folder executing 'git init'. From that point on you'd have to manage your git repository by either git itself (command line) or some other UI. SourceTree works really well for me.
It is a bit late, I know, but this method perfectly works and I hope it is useful for anyone who sees this post from now on.
The procedure is the following:
First step is creating a repository on Github (through github.com)
Move to Eclipse IDE (Git Repositories view) and click "Clone a Git Repository and add the clone to this view". Doing that the project will be somewhere located on the hard disk. Usually, it is stored in C:\Users\username\git\projectName but you are able to change it. This is our local repository.
Once done, press (in Eclipse IDE) File->Import->Projects from Git->Existing local repository(Select the one you cloned before)->Import using the new project wizard->Finish->Java->Java Project->Specify project name (just below the dialog box there is a checked checkbox that says use default location, uncheck it. Here is where you have to specify the directory you chose while cloning the repository previously).->Next->Finish
It should be enough for creating the right directory structure.
I've just recently started using Mercurial and would like to keep my projects as independent from IDE as possible.
Therefore, I would like to only include my src, test src, and doc directory in the repository.
I've managed to only book these directories into the repository by ignoring all project related files.
The problem is that when I then clone it onto another system, Netbeans 7 wants to create a new project from these files. It does so by creating the project file inside of the repo instead of on the cloned name, since it cannot create a project on a directory that already exists.
Is there a standard way of booking in these folders and then when cloning them to create a project from them?
What about creating the project in Netbeans first and the cloning the files into it?
To avoid Mercurial complaining about the clone destination not being empty, use init + pull in the project directory instead of clone, this is equivalent:
$ cd myproject
$ hg init
$ hg pull -u http://example.org/myrepo
You could also just clone into a separate directory and then move all files (including the hidden .hg directory) into the Netbeans project. You could even just move the .hg directory, because that’s really all that Mercurial cares about.
Although actually I’m surprised you can’t start a project that is already on the file system. I’m not familiar with Netbeans, but can’t you import an existing project from the file system?