Conditional includes was a game changer for me. Based on the pwd use a different configuration file. Allowing me to have open source GH settings in all sub dirs of on folder and work git server related settings in another. https://git-scm.com/docs/git-config#_conditional_includes …
-
-
- Kraj razgovora
Novi razgovor -
-
-
A per-project .gitignore seems sensible so other contributors don’t accidentally add files which should have been ignored.
-
There’s a use case for both.
- Još 1 odgovor
Novi razgovor -
-
-
While we are here... learning that “git checkout -“ behaves exactly like “cd -“ was a game changer
-
This zsh func has been so useful for me: gcd() { cd "$(git rev-parse --show-toplevel || echo ".")/$1" } # cd to the top-level of the current git-repo $ gcd # cd to some sub-path within the repo (from anywhere in the repo) $ gcd pkg/auth
- Još 1 odgovor
Novi razgovor -
-
-
The first thing that comes to my mind is ".DS_Store"
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
-
-
The main problem being that then everyone else sharing your project doesn't get the benefit of your .gitignore. I actually would much rather have one duplicated than have different behavior than my peers for a shared repo.
-
actually, I take that back.
@jcbwlkr had a good point with .DS_Store - platform or tool-specific files that get dumped into your directory that other people might not need to care about is a good use for a personal (and global) .gitignore. - Još 1 odgovor
Novi razgovor -
-
-
.DS_Store be gone!
Hvala. Twitter će to iskoristiti za poboljšanje vaše vremenske crte. PoništiPoništi
-
Čini se da učitavanje traje već neko vrijeme.
Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.