Re: [git-users] .gitignore ignored?

[Sascha Manns]

Hello Rusi,

thank you very much for your help. You was right, the issue is now solved.

Greetings
Sascha

Am Freitag, 2. Oktober 2015 06:11:26 UTC+2 schrieb rusi:
>
> On Fri, Oct 2, 2015 at 5:30 AM, Sascha Manns  > wrote: 
> > Hello list, 
> > 
> > actually i'm having some trouble by using git. My .gitignore shows: 
> > 
> > sascha@sascha-desktop:~/RubymineProjects/hoe-manns$ cat .gitignore 
> > Index.yml 
> > hoe-manns.gemspec 
> > .yardoc 
> > SetupConfig 
> > SetupReceipt 
> > README.txt 
> > doc 
> > ChangeLog 
> > pkg 
> > .teamcity 
> > .idea 
> > Changelog 
> > 
> > But a git status says me: 
> > 
> > sascha@sascha-desktop:~/RubymineProjects/hoe-manns$ LANG=C git status 
> > On branch develop 
> > Your branch is up-to-date with 'origin/develop'. 
> > Changes not staged for commit: 
> >   (use "git add ..." to update what will be committed) 
> >   (use "git checkout -- ..." to discard changes in working 
> directory) 
> > 
> > modified:   .idea/workspace.xml 
>
> A file that is in the repo (already) needs to be removed first to be 
> ignored. See: 
>
> http://stackoverflow.com/questions/1139762/ignore-files-that-have-already-been-committed-to-a-git-repository
>  
>
> I prefer this for the task (assuming changing history is ok) 
> https://rtyley.github.io/bfg-repo-cleaner/ 
>

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] .gitignore ignored?

[Sascha Manns]

Hello list,

actually i'm having some trouble by using git. My .gitignore shows:

sascha@sascha-desktop:~/RubymineProjects/hoe-manns$ cat .gitignore 
Index.yml
hoe-manns.gemspec
.yardoc
SetupConfig
SetupReceipt
README.txt
doc
ChangeLog
pkg
.teamcity
.idea
Changelog

But a git status says me:

sascha@sascha-desktop:~/RubymineProjects/hoe-manns$ LANG=C git status
On branch develop
Your branch is up-to-date with 'origin/develop'.
Changes not staged for commit:
  (use "git add ..." to update what will be committed)
  (use "git checkout -- ..." to discard changes in working directory)

modified:   .idea/workspace.xml

no changes added to commit (use "git add" and/or "git commit -a")

Any ideas why it doesn't ignores that file?

Greetings Sascha

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [git-users] .gitignore ignored?

[Rustom Mody]

On Fri, Oct 2, 2015 at 5:30 AM, Sascha Manns  wrote:
> Hello list,
>
> actually i'm having some trouble by using git. My .gitignore shows:
>
> sascha@sascha-desktop:~/RubymineProjects/hoe-manns$ cat .gitignore
> Index.yml
> hoe-manns.gemspec
> .yardoc
> SetupConfig
> SetupReceipt
> README.txt
> doc
> ChangeLog
> pkg
> .teamcity
> .idea
> Changelog
>
> But a git status says me:
>
> sascha@sascha-desktop:~/RubymineProjects/hoe-manns$ LANG=C git status
> On branch develop
> Your branch is up-to-date with 'origin/develop'.
> Changes not staged for commit:
>   (use "git add ..." to update what will be committed)
>   (use "git checkout -- ..." to discard changes in working directory)
>
> modified:   .idea/workspace.xml

A file that is in the repo (already) needs to be removed first to be
ignored. See:
http://stackoverflow.com/questions/1139762/ignore-files-that-have-already-been-committed-to-a-git-repository

I prefer this for the task (assuming changing history is ok)
https://rtyley.github.io/bfg-repo-cleaner/

-- 
You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[git-users] gitignore ignored?

[Mauro Sanna]

Hello.
My .gitignore is:

*.iws
*Db.properties
*Db.script
.settings
stacktrace.log
/*.zip
/plugin.xml
/*.log
/*DB.*
/cobertura.ser
.DS_Store
/target/
/out/
/web-app/plugins
/web-app/WEB-INF/classes
/.link_to_grails_plugins/
/target-eclipse/

When I push my commits I see target and its subdirs in the repository.
But target is gitignored, why is it pushed?

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Re: [git-users] gitignore ignored?

[Konstantin Khomoutov]

On Fri, 27 Sep 2013 00:53:21 -0700 (PDT)
Mauro Sanna mrsan...@gmail.com wrote:

[...]
 When I push my commits I see target and its subdirs in the repository.
 But target is gitignored, why is it pushed?

There are several misunderstandings here:

1) Mechanisms for ignoring files in Git have nothing to do with pushing
   and fetching: these operations manipulate existing commits and
   references pointing at them.

   It's index updates (`git add`) and, in certain cases, work tree
   oprtations (`git rm`, `git clean` etc) which consider ignore lists
   (so that, say `git add '*'` won't add auto-built cruft added to
   an ignore list).

2) Mere updating of a branch in a remote repo does not do anything
   to the subdirs in the repository because such subdirs only
   occur in the work tree of a non-bare repository, and the push
   operation is not concerned about the work tree (short of respecting
   the receive.denyCurrentBranch configuration variable which forbids
   updating of a branch which is currently checked out in a non-bare
   repository).

   So it might be that if you actually *deleted* already tracked
   unwanted files and recorded a commit which does not contain them
   anymore and then arranged for them to be excluded by the Git file
   ignoring mechanism, and then updated a remote branch with your
   commit, you now need to actually update your work tree to the new
   state of the updated branch -- for instance, by doing

   git reset --hard

   in the work tree (provided the updated branch is what is currently
   checked out, -- otherwise a mere `git checkout that_branch` would
   suffice).

-- 
You received this message because you are subscribed to the Google Groups Git 
for human beings group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.