The way to “fix” .gitignore file is after making in a .gitignore file, not matter if you working with BitBucket, GitHub, or any other service, to fix the issue you need to execute these commands:

git rm -rf --cached .
git add . 
git commit -m 'fixed gitignore'

git rm -r --caced – will remove the files completely from the index (just like add is adding to the index).

git add . – will add all of the files (this is the dot, dot means all).

git commit -m 'fixed gitignore' – will commit the the changes with the label of: “fixed gitignore”, this can be whatever you want, for me, each time I start a project and do the first commit, I ALWAYS forget to add/change/create the .gitignore file, so my two first commits are always: ‘inital commit’ and ‘fixed .gitignore’.

The post Making .gitignore to take effect (gitignore is not working) appeared first on SideCode.

cd /path/to/your/repo

Step 2: Connect your existing repository to Bitbucket

git remote add origin https://PATH_TO_YOUR_REPO

git push -u origin master

The post Bitbucket – Setup Git on a Remote Server For an existing Repo appeared first on SideCode.

git init

run (to connect your server with the cloud repo)

git remote add origin https://PATH_TO_YOUR_REPO

Then if you want your production server to always pull from the remote origin (so you will be able to run git pull instead of git pull origin master)
You need to add this to your /.git/cofig, you can do this like this:

 git config branch.master.remote origin
 git config branch.master.merge refs/heads/master

Now you can run git pull, and it will automatically pull from your master branch.

If you also git to remember your password (so you won’t need to type it with every “git pull”)

enable credentials cache: (make sure you have git version > 1.7.12.1, which you probably have).

git config --global credential.helper cache

The post Setting Git on a Production Server appeared first on SideCode.

This is because you are on a Mac, and you upgraded to macOS Sierra.

To fix this, all you need to do is update/install Xcode.
run this command in the terminal:

xcode-select --install

Run the command, agree to the agreement and install Xcode.
This will fix the issue.

The post Git Error – invalid active developer path (also called, did you upgraded to macOS Sierra?) appeared first on SideCode.

git init

# Starting BitBucket repo

# It’s Pretty much the same process for any other git service like GitHub.

BTW, the main difference between GitHub and BitBucket services is that in Github it’s free to create public reops, and in BitBucket it’s free to create private repos.
(Public repos, the whole world can see. Private repos, are only yours to see, or anyone else you choose to share it with).

Create a repo in the web interface (BitBucket Website).
Create a folder on local machine (the root folder that will contain your project).
let’s say ~/username/sites/myWebsite
In the command line do:

cd ~/username/sites/myWebsite 
git init 
git add . 
git commit -m ‘Inital Commit’
git remote add origin <repo-url> 
git push origin master 

Explanation:

git init – start a git repo inside your folder.
git add . – Add all of the current folder files to your next commit.
git commit -m ‘Inital Commit’ – “save” or commit, create a commit with the name “Inital Commit” (you can give it any name you want).
git remote add origin <repo-url> – here copy and paste the repo url from BitBucket
git push origin master – push your changes, (your new commit) to the BitBucket Repo.

# Removing all latest changes (deleting them)

If you made some changes, you don’t want them (at all), and just want to checkout a different commit, (go back in time, if you will).
you will get an error as long as there are unstated files, to remove them do:

git clean -f -d # remove untracked files

# .Gitignore

IF you want to commit all files except certain files (like config files with Passwords, or just trash files like .codekit) that you only need on your local machine. You need to tell git to ignore these files, the way to do it is to create a .gitignore file.

Create a .gitignore file

nano .gitignore (or just don't be weird and create a file in a different way).

add whatever you want git to ignore like:

.DS_Store // this will ignore the .DS_Store files that is created by MAC OS.

IF you want to ignore a complete dir with all of the files in the dir and subdirectories

.idea/

If you want to ignore all files with some extension do (ex: ignore all .log files):

*.log

If you want to add comments to the .gitignore, (notes for yourself, because you keep forgeting what you are doing) do:

# this is a comment

then to make the .gitignore take effect do:

git rm -r --cached .
git add .
git commit -m "fixed untracked files"

# General Commands

git status – get the status of a git repo

git log – see commits of the repo

git init – start a git repo

git add . – stage all changed files to the next commit

git commit -m ‘title of commit’ – committing a repo with a title.

git checkout <name of branch or master> – checkout different commit/branch

git pull – pull changes of repo from origin reposetory

git push – push changes of repo to origin reposetory

git checkout -f – will checkout master with force (ignore all changes, you will lose all untracked files).

git clean -fd – remove untracked files, -f – force it, -d – remove also directories that are untracked.

The post Git – General Notes and Basic commands appeared first on SideCode.

# Revert changes to modified files.
git reset --hard

# Remove all untracked files and directories. (`-f` is `force`, `-d` is `remove directories`)
git clean -fd

The post Git – Remove Unsaved Changes appeared first on SideCode.