If I have a local repository on my mac desktop, how can I push it to GitHub directly from XCode 5.1 without using the terminal? I know you can do it with this:
cd <directory of xcode>
git remote add origin git#github.com:YOUR-REPOS-NAME
git push -u origin master
You need to add a remote.
Source Control > Select your project > Configure...
Then hit the +, and you'll be able to add your remote.
After this you'll then be able to go to (after you have performed a commit)
Source Control > Push...
All features can be accessed from this menu, or by right-clicking files in the project navigator
Use the Xcode 'Source Control' menu drop down. Here you can "checkout" and then later "push" source code to a git repository, such as one hosted on GitHub.
Related
Set up GIT via SSH in my Spring STS Tool (based on Eclipse).
It worked fine for months - could pull/push/commit files from the Eclipse UI. I.e., right-click on the repo, then Team and git action.
This has stopped working - for any operation on any repo I get this error:
Pulling 1 repository
git#gitlab.techopscloud.com:.git: Session is being closed
Via the command line, the git works fine as before. Any idea how to fix it in the UI?
How do I re-configure the GIT setup in Eclipse?
Thanks
To re-configure the Git setup in Eclipse, follow these steps:
Go to Window > Perspective > Open Perspective > Other...
Select Git and click OK.
In the Git perspective, go to Window > Show View > Other...
Select Git Repositories and click OK.
In the Git Repositories view, click the Clone a Git Repository
button.
Enter the repository URL, select Protocol as SSH and provide the
required credentials.
Finish the clone process and your repository should now be available
in Eclipse.
This should re-configure the Git setup in Eclipse and fix the error you're encountering. If the error persists, you may need to check the settings of your SSH key or the connection to the Git server.
I created a new project and try to commit it from source control tab. But the commit widow does not show any files.
It is possible that your project is not being tracked by git. To enable tracking, you need to open the project directory in command prompt and run following command -
git init
This will initialise git in your project repo and start tracking your files.
I want to put my current project on GitHub, but within my Source Control Navigator, it shows Branches. After double clicking the Initial Commit within master, it's showing a different project than what is currently open on Xcode.
Eventually I want to put the Xcode project on GitHub, but even if I try, it puts whatever is in master, which is incorrect. How do I fix this?
Edit:
It took a few Terminal commands, and then I was able to go to the Source Control menu >> Commit without errors.
xcrun git config --global user.email you#whatever.com
xcrun git config --global user.name "Your Name"
This put the correct version of the project on GitHub after I created a remove. Unfortunately, my master(current) is still incorrect and it includes that on GitHub for some reason.
Here are some screenshots of my Source Control Navigator. I only want first master displayed in the root folder or remote >> origin. Within the Branches folder, the only master shown is incorrect.
I moved a hidden ".git" (system) folder outside my main project folder. I then could create a new repository within the Source Control Navigator, create a new remote and the appropriate projects are visible in GitHub.
I have an Xcode project one local and one remote repository. Firstly, there was a problem in current version and I decided to change local repository's head using terminal. Xcode fetched everything and I continued working on the project. When I decided to commit changes, Xcode gave me an error like this: "error: src refspec (detached from ) does not match any.error: failed to push some refs to [repository address]". After, I decided to create a new remote repository and try to make initial commit of this project. I added remote to Xcode and now it crashes even if I open "remotes" tab. I use bitbucket as my remote repo.
Question: is it possible to fix this, or it is easier to copy all the contents of the project to another one and commit new one? Thanks for replies.
I had the same problem: the local git repo was created from command line (from terminal app) and not from within Xcode, Xcode would crash every time even when clicking on the remote tab. I have a different solution that may be easier:
1)Commit and Push all changes with your current project from your local Xcode-non-compatible repo
2) Re-open Xcode (close it if it's open) and select "Check out an existing project" from Xcode
*If you don't see this Xcode startup screen, go to Source Control->Check Out...
3)Select the remote repo then
4)Select a NEW directory for the checkout destination
Now you will have a project set up and compatible with Xcode!
Solved:
Create new empty project, then copy all the files from previous one. Create new repository, absolutely clean. Push there.
It seems that Xcode had a conflict when local repository's head was changed using command line and git. So, this is as warning for users who got the same situation.
When I set up a new project in Xcode 4, and select "Create local git repository for this project," all seems well enough. I'm able to commit files from the Organizer (it would appear.) However, in the Project Manager, the "Source Control" menu options (commit, etc.) are all grayed out, except for "Repositories" which of course just takes me to the organizer.
Furthermore, in the Project Manager window, I don't see any icons by file names indicating if they're changed, committed etc. like I see in the screenshots in the Xcode 4 documentation.
I've tried this with both a project that's connected to Github, and one that's just using a local repository, and I've still yet to see those options not be grayed out. Any suggestions?
I discovered the cause of this problem is that I was saving projects in /Developer.
Turns out, that's a big no-no. Not only does it break git integration in the way described in the original question, as well as breaking other features such as Xcode 4's refactoring functionality, it also runs the risk of deleting all of your work when you install an update. Once I started saving projects outside of /Developer, all the git functions in Xcode 4 started working as expected.
Bottom line: Don't keep projects in /Developer.
This can be a bit confusing. Apples documentation here:
http://developer.apple.com/library/mac/#documentation/ToolsLanguages/Conceptual/Xcode4UserGuide/SCM/SCM.html
Has a great way to activate the source control via the command line:
To set up a Git repository from the command line . . .
Use the cd command to switch to your project folder, making it the current working directory.
Enter git init to create an empty repository.
Enter git add . to copy your project files into the repository.
Enter git commit -m "Initial commit." to commit all the files.