IntelliJ has no option to click on a file and choose &quot;*Add to .gitignore*&quot; like Eclipse has. 

The quickest way to add a file or folder to *.gitignore* without typos is:

1. Right-click on the file in the project browser and choose &quot;*Copy Path*&quot; (or use the keyboard shortcut that is displayed there).
2. Open the *.gitignore* file in your project, and paste.
3. Adjust the pasted line so that it is relative to the location of the *.gitignore* file.

**Additional info**: There is a [*.ignore*][1] **plugin** available for IntelliJ which adds a &quot;Add to .gitignore&quot; item to the popup menu when you right-click a file. It works like a charm.


  [1]: https://plugins.jetbrains.com/plugin/7495?pr=idea

Intellij had `.ignore` plugin to support this.
https://plugins.jetbrains.com/plugin/7495?pr=idea

After you install the plugin, you right click on the project and select `new` -&gt; `.ignore file` -&gt; `.gitignore file (Git)`
[![enter image description here][1]][1]

Then, select the type of project you have to generate a template and click `Generate`.
[![enter image description here][2]][2]


  [1]: http://i.stack.imgur.com/bOoGR.png
  [2]: http://i.stack.imgur.com/3S6ca.png

You can create file .gitignore and then Idea will suggest you install plugin

Here is the screen print showing the options to ignore the file or folder after the installation of the .ignore plugin. The generated file name would be .gitignore
[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/OTqdJ.png

I&#39;m using intelliJ 15 community edition and I&#39;m able to right click a file and select &#39;add to .gitignore&#39;

right click on the project create a file with name .ignore, then you can see that file opened.

at the right top of the file you can see install plugins or else you can install using plugins(plugin name -  **.ignore**).

Now when ever you give a right click on the file or project you can see the option call add to .ignore

I want to create a table of **325** column:

    CREATE TABLE NAMESCHEMA.NAMETABLE 
    (	
          ROW_ID TEXT NOT NULL ,        //this is the primary key

    324 column of these types:
          CHAR(1), 
          DATE, 
          DECIMAL(10,0), 
          DECIMAL(10,7), 
          TEXT, 
          LONG,
 
    ) ROW_FORMAT=COMPRESSED;

I replaced all the VARCHAR with the TEXT and i have added **Barracuda** in the my.ini file of MySQL, this is the attributes added:

    innodb_file_per_table=1
    innodb_file_format=Barracuda
    innodb_file_format_check = ON

but i still have this error:

    Error Code: 1118
     Row size too large (&gt; 8126). Changing some columns to TEXT or BLOB may help. In current row format, BLOB prefix of 0 bytes is stored inline.

EDIT: I can&#39;t change the structure of the database because it&#39;s legacy application/system/database. The create of a new table, it&#39;s an export of the legacy database.

EDIT2: i wrote this question that is similar to others but inside there are some solution that i found on internet like VARCHAR and Barracuda, but i still have that problem so i decided to open a new question with already the classic answer inside for seeing if someone have other answers

MySQL: Error Code: 1118 Row size too large (&gt; 8126). Changing some columns to TEXT or BLOB

I&#39;m trying to build:
https://github.com/kanzure/nanoengineer

But it looks like it errors out on:

    gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/include/python2.7   -std=c99 x86_64-linux-gnu-gcc -pthread -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall -Wstrict-prototypes -fPIC -MT libstructcompare_a-structcompare.o -MD -MP -MF .deps/libstructcompare_a-structcompare.Tpo -c -o libstructcompare_a-structcompare.o `test -f &#39;structcompare.c&#39; || echo &#39;./&#39;`structcompare.c
    gcc: error: x86_64-linux-gnu-gcc: No such file or directory

`x86_64-linux-gnu-gcc` definitely exists in */usr/bin* (It&#39;s a symlink) and the target definitely exists as well. It looks to me like the Makefile wasn&#39;t generated correctly, perhaps there is a flag that should be passed before specifying x86_64-linux-gnu-gcc? I am unsure as well what specifying `x86_64-linux-gnu-gcc` is supposed to accomplish.

Finally, this makefile was generated by configure, so once we narrow down the cause of the error, I&#39;ll have to figure out what files to modify in order to fix this. (I&#39;m a CMake kind of guy myself, but of course I didn&#39;t choose the build system for this project.) My OS is Debian.

I&#39;ve tried building this branch as well:
https://github.com/kanzure/nanoengineer/branches/kirka-updates

If you can try getting this to build on your system, I would greatly appreciate it! Thanks!

Debugging the error &quot;gcc: error: x86_64-linux-gnu-gcc: No such file or directory&quot;

I try to switch from Eclipse to IntelliJ IDEA. I have a project that uses Git and I want to quickly add files to *.gitignore* file. In Eclipse I can right click on a file/directory and choose &#39;*Add to .gitignore*&#39;.

Is there anything like this in IntelliJ IDEA or I have to edit the file manually?

How to add files/folders to .gitignore in IntelliJ IDEA?

I try to switch from Eclipse to IntelliJ IDEA. I have a project that uses Git and I want to quickly add files to .gitignore file. In Eclipse I can right click on a file/directory and choose 'Add to .gitignore'.
Is there anything like this in IntelliJ IDEA or I have to edit the file manually?

I am very new to Git and I am planning to contribute to some open-source project on GitHub after discovering a small error in it. Upon forking it and fixing the error, I purposed a pull request and I noticed this showing up:  

&gt; Failed — The Travis CI build failed

Looking into the details I discovered it was caused by `Could not find .travis.yml`, which made perfect sense since I had not signed in to Travis Cl with and add .travis.yml to the repository.

This is my first time hearing about Travis and what that is known as continuous integration. And it sounds pretty cool so in order to learn more about it, I looked it up on Wikipedia.


&gt;  Travis CI is a hosted, distributed continuous integration service
&gt; used to build and test projects hosted at GitHub. Travis CI automatically detects when a commit has been made and pushed to a GitHub repository that is using Travis CI, and each time this happens, it will try to **build the project and run tests**. This includes commits to all branches, not just to the master branch.

My current understanding of Travis CI is that what it does is automatically pushing the project upon `git commit -am &quot;..&quot;` and I don&#39;t quite understand some part of it.

1. By **building the project and run tests**, what tests is it going to run? And how is it going to &quot;build&quot; the project? (like compiling it to binary?)

2. It states that &quot;This includes commits to all branches&quot; - but what if I don&#39;t want to commit to all branches?

3. Is it alright if I don&#39;t use Travis Cl at all? Under what circumstances is it best to use it (or it must be used)? 


Trying to understand what Travis CI does and when it should be used

Here&#39;s a workflow that I commonly deal with at work.

    git checkout -b feature_branch
    # Do some development
    git add .
    git commit
    git push origin feature_branch

At this point the feature branch is up for review from my colleagues, but I want to keep developing on other features that are dependent on `feature_branch`.  So while `feature_branch` is in review...

    git checkout feature_branch
    git checkout -b dependent_branch
    # Do some more development
    git add .
    git commit

Now I make some changes in response to the code review on feature_branch

    git checkout feature_branch
    # Do review fixes
    git add .
    git commit
    git checkout dependent_branch
    git merge feature_branch

Now this is where we get have problems.  We have a squash policy on master, which means that feature branches that are merged into master have to be squashed into a single commit.

    git checkout feature_branch
    git log # Look for hash at beginning of branch
    git rebase -i  first_hash_of_branch # Squash feature_branch into a single commit
    git merge master

Everything is cool, except with `dependent_branch`. When I try to rebase dependent branch onto master or try and merge master into it, git is confused by the re-written/squashed history and basically marks every single change in `depedendent_branch` as a conflict.  It&#39;s a PITA to go through and basically re-do or de-conflicticize all of the changes in `dependent_branch`. Is there some solution to this?  Sometimes, I&#39;ll manually create a patch and apply it off a fresh branch of master, but if there&#39;s any real conflicts with that, its even worse to fix.

    git checkout dependent_branch
    git diff &gt; ~/Desktop/dependent_branch.diff
    git checkout master
    git checkout -b new_dependent_branch
    patch -p1 &lt; ~/Desktop/dependent_branch.diff
    # Pray for a clean apply.

Any ideas?  I know this happens because of the re-written history during the squash, but that&#39;s a requirement that I can&#39;t change.  What&#39;s the best solution / workaround?  Is there some magic I can do?  Or is there a faster way to do all the steps involved with manually creating the diff?
    
    

Merging a branch of a branch after first branch is squashed when merged to master

I just cloned a git repository and checked out a branch. I worked on it, and then decided to remove all my local changes, as I wanted the original copy.


In short, I had to do the following two commands to remove my local changes

    git checkout .

    git clean -f

**My question is,**

(1) Is this the correct approach in getting rid of local changes, or else please let me know the correct approach.

(2) when do we use `git reset --hard` as i am able to reset even without this command


Thanks


***Solution : Major Edit(s): 03/26 : *** 
Replaced many of vague terms with git specific terminology
 [tracked/untracked/staged/unstaged]

There could be only three categories of files when we make local changes:

&gt; Type 1. Staged Tracked files
&gt; 
&gt; Type 2. Unstaged Tracked files
&gt; 
&gt; Type 3. Unstaged UnTracked files a.k.a UnTracked files

- Staged - Those that are moved to staging area/ Added to index
- Tracked - modified files
- UnTracked - new files. Always unstaged. If staged, that means they are tracked.

**What each commands do:**

1. `git checkout .` - Removes Unstaged Tracked files ONLY [Type 2]

2. `git clean -f` - Removes Unstaged UnTracked files ONLY [Type 3]

3. `git reset --hard` - Removes Staged Tracked and UnStaged Tracked files ONLY[Type 1, Type 2]

4. `git stash -u` - Removes all changes [Type 1, Type 2, Type 3]


**Conclusion:**

It&#39;s clear that we can use either 

    (1) combination of `git clean -f` and `git reset --hard` 

   OR

    (2) `git stash -u`

to achieve the desired result.

Note: Stashing, as the word means &#39;Store (something) safely and secretly in a specified place.&#39; This can always be retrieved using `git stash pop`.
So choosing between the above two options is developer&#39;s call.

Thank you Christoph and Frederik Sch&#248;ning.

**Edit: 03/27**

I thought it&#39;s worth putting the &#39;*beware*&#39; note to `git clean -f`

`git clean -f`

There is no going back. Use `-n` or `--dry-run` to preview the damage you&#39;ll do.

If you want to also remove directories, run `git clean -f -d`

If you just want to remove ignored files, run `git clean -f -X`

If you want to remove ignored as well as non-ignored files, run `git clean -f -x`

reference : more on `git clean` : https://stackoverflow.com/questions/61212/removing-untracked-files-from-your-git-working-copy?rq=1

**Edit: 05/20/15**

*Discarding all local commits on this branch* [Removing local commits]

In order to discard all local commits on this branch, to make the local branch identical 
to the &quot;upstream&quot; of this branch, simply run `git reset --hard @{u}`

Reference: http://sethrobertson.github.io/GitFixUm/fixup.html

or do `git reset --hard origin/master` [if local branch is `master`]


**Note: 06/12/2015**
This is **not** a duplicate of the other SO question that&#39;s marked as duplicate. This question address how to remove local GIT changes [remove a file added, remove changes added to existing file etc and the various approaches; Where in the other SO thread only address how to remove local commit. If you added a file, and you want to remove that alone, then the other SO thread doesn&#39;t discuss about it. Hence this is not a duplicate of the other one]

**Edit: 06/23/15**

How to revert a commit already pushed to a remote repository?

    $ git revert ab12cd15

**Edit: 09/01/2015**

Delete a previous commit from local branch and remote branch

Case: You just commited a change to your local branch and immediately pushed to the remote branch,
Suddenly realized , Oh no! I dont need this change. Now do what?

`git reset --hard HEAD~1`     [for deleting that commit from local branch]

`git push origin HEAD --force` [both the commands must be executed. For deleting from remote branch]

Whats the branch ? Its the currently checked out branch.

**Edit 09/08/2015** - Remove local git **merge**:

I am on `master` branch and merged `master` branch with a newly working branch `phase2`

    $ git status
    # On branch master
    
    $ git merge phase2
    
    $ git status
    # On branch master
    # Your branch is ahead of &#39;origin/master&#39; by 8 commits.

Q: How to get rid of this merge?
Tried `git reset --hard`   and `git clean -d -f`
Both didn&#39;t work.

The only thing that **worked** are any of the below ones:

    $ git reset --hard origin/master

or

    $ git reset --hard HEAD~8

or

`$ git reset --hard 9a88396f51e2a068bb7`  [sha commit code - this is the one that was present before all your merge commits happened]



Various ways to remove local Git changes

Is this not possible to create somme sub-sub-folder in a repo on a server? 

if i do:

    git push origin dev/master 

everything work find

but if i do

    git push origin dev/sub/master

i got this:

    error: &#39;refs/heads/dev/sub&#39; exists; cannot create &#39;refs/heads/dev/sub/master&#39;

i checked with `git branch -r` and directly with ssh, there isn&#39;t dev/sub folder already created.


what&#39;s wrong?


git push: refs/heads/my/subbranch exists, cannot create

I&#39;m having trouble setting up sublime as my git commit message editor.

Using:

    git config --global core.editor &quot;subl&quot;

Error:
error: cannot run subl: No such file or directory
error: unable to start editor &#39;subl&#39;
Please supply the message using either -m or -F option.

subl work perfectly otherwise.


Setting up sublimetext 3 as git commit text editor

I was testing out some new features of Java 8 and copied the example into my IDE (Eclipse originally, then IntelliJ) as shown [here][1]


Eclipse offered no support whatsoever for lambda expressions, and IntelliJ kept reporting an error 

&gt; Lambda expressions not supported at this language level

I would like to know if this is a problem with my install, the code, or support.


  [1]: http://docs.oracle.com/javase/tutorial/java/javaOO/examples/RosterTest.java

Java &quot;lambda expressions not supported at this language level&quot;

How do I configure Android Studio (or Intellij generally) to correctly generate getters and setters for member variables with prefixes?

If I have a class 

    public class Foo{
        int mBar;
    }

I want it to create `getBar()` instead of `getMBar` when I do `Refactor-&gt;Encapsulate` or `Generate`

**EDIT**

I found the way to do it per-project basis: You just go `File-&gt;Settings-&gt;Project Settings-&gt;Code Style`

But it created a settings file somewhere in my project directory. 

I want a solution which allows me to do it once for all projects, present and future. 

Intellij (Android studio) member variable prefix

Is it possible to step backwards through executed code in a debug session?

For example I step over a method called `abc()` expecting to get `12` but after re-checking the value returned I notice it&#39;s `5` instead of `12`. How can I step back to where I was before and step into the method to see what is going on?  I know you can do this in visual studio but I can&#39;t find how to do this in intelliJ.  

How to step one step back in IntelliJ?

How would be possible to assign a shortcut for word wrap like as sublime text do? i.e. if the code line is too long it should be automatically break to the next line. [wikipedia.org.org/Word_wrap][1]

![This code should be wrapped out][2]


  [1]: http://en.wikipedia.org/wiki/Word_wrap
  [2]: http://i.stack.imgur.com/DVOwA.png

Code Wrap IntelliJ?

I&#39;m trying to use Android Studio, and the first time I boot it up, it takes like 45 MINUTES to compile... If I don&#39;t quit the application, it is okay - each subsequent compilation/running the app will take around 45 seconds.

I&#39;ve tried to check some of my caches: there&#39;s a `.gradle/caches` folder in my home directory, and it&#39;s contains 123 MB.

There&#39;s also a `.gradle` folder in my project folder... one of the `taskArtifacts` was like 200 MB. I&#39;m scared to just randomly nuke them both. What parts of the folders are safe to delete?

Is there a better explanation for why my Android Studio is taking forever to run the `gradle assemble` task upon first time loading the application?

Do I also have to clear the intellij cache too?

How to clear gradle cache?

I am a bit confused about the pros and cons of using `.git/info/exclude` and `.gitignore` to exclude files.

Both of them are at the level of the repository/project, so how do they differ and when should we use `.git/info/exclude` ?

When would you use .git/info/exclude instead of .gitignore to exclude files?

**What I did:**

I think there were some weird configurations from the github gui that caused this issue and prevented me from being able to easily use git from command line or even git-bash.

I ended up just uninstalling github and git then reinstalling just git for windows. I now have everything running off the command line(except ssh which I run from git-bash). Much easier and more reliable that the github gui.

Thanks to mu 無 for taking the time to try to figure this out. I didn&#39;t end up using his answer, but if I hadn&#39;t needed to do a reinstall of git it would have been what I needed to do.

---

I am using the github gui on my local machine. I just noticed that a commit I was about to make was going to update all of my recently update node modules. I set up my .gitignore to ignore the entire `node_modules/` directory.

I&#39;m not sure what to do about this. All the file types I included in .gitignore were ignored. It&#39;s just the directories that it seems to ignore.

Here is my .gitignore file:

    #################
    ## Sublime Text
    #################
    
    *.sublime-project
    *.sublime-workspace
    
    #################
    ## Images
    #################
    
    *.jpg
    *.jpeg
    *.png
    *.gif
    *.psd
    *.ai
    
    #################
    ## Windows detritus
    #################
    
    # Windows image file caches
    Thumbs.db
    ehthumbs.db
    
    # Folder config file
    Desktop.ini
    
    # Recycle Bin used on file shares
    $RECYCLE.BIN/
    
    # Mac crap
    .DS_Store
    
    #################
    ## Directories
    #################

    dev/
    cms/core/config/
    node_modules/

.gitignore is not ignoring directories

I&#39;ve read the docs on this several times over and I still don&#39;t completely get the differences between these different commands. Maybe it&#39;s just me, but the documentation could be more lucid:

http://git-scm.com/docs/gitignore

https://help.github.com/articles/ignoring-files

Moreover, a lot of the commentary on this subject seems to use the words &quot;indexed&quot;, &quot;committed&quot;, &quot;tracked&quot; somewhat loosely, which makes the differences between these three less clear.

My current (admittedly limited) understanding:

 - Files matched in `.gitignore` will not be tracked in the future.
   (Though they may have been tracked previously.) This means that they
   won&#39;t ever show up in a future `git status` list as changed.
   _However, future changes will still be synced with remote repos_. In other words, the files are still &quot;indexed&quot;, but they are not &quot;tracked&quot;.
   Because a `.gitignore` file is in the project directory, the file
   itself can be versioned.
   
 - Files matched in `.git/info/exclude` will also not be &quot;tracked&quot;. In
   addition, these files will not ever be remotely synced, and thus will
   never be seen in any form by any other users. These files should be files that
   are specific to a single user&#39;s editor or workflow. Because it is in the `.git`
   directory, the `exclude` file can&#39;t itself be versioned.
   
 - Files that have had `assume-unchanged` run on them also don&#39;t show up in `git status` or `git diff`. This seems similar to `exclude`, in that these files are neither &quot;indexed&quot; nor &quot;tracked&quot;. However, the last version of the file to be committed before `assume-unchanged` will remain visible to all users in the repo.

My questions:
================

 1. Is the above interpretation correct? Please correct me.
    
 2. If a file has already been in a commit, what is the functional
    different between matching it in `.exclude` and running
    `assume-unchanged` on it? Why would one prefer one approach to
    another?
    
 3. My basic use case is that I want to avoid sorting through diffs on
    compiled files, but I still want those compiled files synced along
    with the source files. Will a `gitignore`&#39;d file still be pushed? If not, how to manage final deployment of the compiled files?

Thanks in advance for any help.

git ignore vs. exclude vs. assume-unchanged

I&#39;m trying to understand more clearly the `.gitignore` syntax, and in particular as far as [https://github.com/github/gitignore][1] gitignores are concerned.

I see that the leading slash is used to match only pathnames relative to the location of the `.gitignore` file (from [http://git-scm.com/docs/gitignore][2]):

&gt; A leading slash matches the beginning of the pathname. For example, &quot;/*.c&quot; matches &quot;cat-file.c&quot; but not &quot;mozilla-sha1/sha1.c&quot;.

But what happens when i remove the leading slash? As far as what i understood, there are two cases:

 1. If the pattern does not contain a slash (or it contains only a trailing slash, which means that it should match a directory), the search is performed inside the entire directory tree. For example, the pattern `dir/` will match `&lt;root&gt;/dir`, `&lt;root&gt;/a/dir`, `&lt;root&gt;/a/b/c/.../dir`, etc., where `&lt;root&gt;` is the location of the `.gitignore` file.
 2. If the pattern contains a slash, which is not in the trailing position (it&#39;s not the last character), then it is matched only with pathnames relative to the `.gitignore` file location.

These are the examples i made to check this behaviour:

    # Directory structure:
    &lt;root&gt;
    ├─ dir/
    │   └─ test
    ├─ src/
    │   ├─ dir/
    │   │   └─ test
    test file is there only because Git does not track empty directories.

First test:

    # .gitignore
    dir/

    # git status
    nothing to commit

So Git is ignoring both `dir` directories. This is consistent with case number 1: the pattern has no slashes (except for the trailing one), so Git is watching the entire directory tree, ignoring everything that matches the pattern.

Second test:

    # .gitignore
    /dir/

    # git status
    Untracked files:
        src/

Here, Git is ignoring only the `dir` directory directly beneath the root directory, thanks to the leading slash in the pattern.

Third test:

    # .gitignore
    dir/*

    # git status
    Untracked files:
        src/

This is consistent with the case number 2: the pattern has some slash inside it, so it is considered as a pathname starting from the root directory.

Now it&#39;s time for the real question. Let&#39;s consider [this gitignore file][3]: when they ignore the directory `downloader/`, for example, aren&#39;t they actually ignoring every single `downloader` directory found in the entire directory tree? This is what i&#39;m driven to think since what i saw about Git&#39;s workings before.

So if i happen to have a custom module with a `downloader` directory inside of it, will it be unexpectedly ignored as well as the regular one in the root of Magento? This is a bit of a rethorical question because it actually already happened to me, producing a really hard to find bug.

So, in the Magento `.gitignore` file (which i&#39;m referring to only as an example, btw) a lot of the patterns contain slashes, so they are correctly matched against pathnames starting from the root, but there are a few cases, like `downloader/` or `errors/` that, if i&#39;m not mistaken, are potentially dangerous, and which should probably be changed to `/downloader/` and `/errors/`.

As a more general question, should i always use the leading slash for patterns not containing slashes (except for the trailing one) when i want to select a pathname explicitly starting from root, and not to use it for patterns containing slashes, or should i always use the leading slash for clarity? What do you think about it?

Thank you for reading and sorry for the long post.


  [1]: https://github.com/github/gitignore
  [2]: http://git-scm.com/docs/gitignore
  [3]: https://github.com/github/gitignore/blob/master/Magento.gitignore

When to use leading slash in gitignore

In the root of my project I have a `foo` folder. Inside the `foo` folder I have a `bar` folder. I would like to ignore all changes to all files inside my `bar` folder. I have this in my `gitignore`:

    /foo/bar

The folder is checked: it exists and it has the files to be ignored. `gitignore` is `commit`ted. However, I have a file where I make a moification and is inside my `bar` folder. When I type

    git status

inside my `git bash` I see the file which should have been ignored. What could be the reason and how can I successfully ignore all files inside my bar folder?

Note, that the files were previously ignored with the same line, but I had to temporarily remove that line to `commit` something on the server. After the `commit`, I put back the line into the `gitignore`. This was a while ago, but now I have observed that the files will be in `git status`. I would expect to be able to modify the ignored files without they appearing in the `git status`.



Content Type	Original Author	Original Content on Stackoverflow
Question	piotrek	View Question on Stackoverflow
Solution 1 - Git	Rolf	View Answer on Stackoverflow
Solution 2 - Git	biniam	View Answer on Stackoverflow
Solution 3 - Git	nanotexnik	View Answer on Stackoverflow
Solution 4 - Git	TechPassionate	View Answer on Stackoverflow
Solution 5 - Git	mancini0	View Answer on Stackoverflow
Solution 6 - Git	Pavan	View Answer on Stackoverflow

How to add files/folders to .gitignore in IntelliJ IDEA?

Git Problem Overview

Git Solutions

Solution 1 - Git

Solution 2 - Git

Solution 3 - Git

Solution 4 - Git

Solution 5 - Git

Solution 6 - Git

Debugging the error "gcc: error: x86_64-linux-gnu-gcc: No such file or directory"

MySQL: Error Code: 1118 Row size too large (> 8126). Changing some columns to TEXT or BLOB

Attributions