What Changes the Most · jj log --no-graph -r 'ancestors(trunk()) & committer_date(after:"1 year ago")' \ -T 'self.diff().files().map(|f| f.path() ++ "\n").join("")' \ | sort | uniq -c | sort -nr | head -20 Who Built This More on news.ycombinator.com

I have a question about adding files in git. I have found multiple stackoverflow questions about the difference between git add . and git add -a, git add --all, git add -A, etc. But I've been unabl... More on stackoverflow.com

git add * instructs your shell to expand the glob. Whatever the shell expands that to is passed to git add. This can have a variety of effects since git add accepts pathspecs, not filenames, and certain "magic" pathspecs have special behaviour. For instance, a pathspec that begins with :^ can be used to negate matches (e.g. git add file.* :^file.jpg could be used to add all filenames matching file.*, but not add file.jpg). If you must get the shell to do the globbing (described below are some ways in which you can avoid having the shell perform the globbing), you could consider using git add -- * instead. This won't avoid the "magic" pathspec issue, but it will avoid any issues with filenames that happen to have a leading hyphen (just imagine how annoying it would be to have a file named -A). git add . instructs Git to add and (on modern versions of Git) remove files from the index so that it matches the contents of the current directory, and recursively all subdirectories. git add -A is identical to git add . (edit: when run from the top directory) on modern versions of Git. As noted above, older versions of Git did not remove files from the index with git add ., but they did with git add -A. You missed one: git add '*'. This instructs Git to perform the globbing instead of your shell. This has two effects. First, it means that filenames that just happen to be "magic" pathspecs won't actually invoke their magic (i.e. if a file is named :^file.jpg it won't do that negation thing I described above). Second, the globbing behaves slightly differently from the shell: in particular, * and ? can match a directory separator, which means git add '*.txt' would actually add all files ending with .txt in the current directory and any descendent directory. More on reddit.com

What is the purpose of this if anyone I am working with on a specific project, wont be able to see my staging or commits on GitHub until I push. You might want to see those commits. They can be used as checkpoints in your code. Maybe you are tasked with building out an entirely new site feature, but you only have time to flesh out the persistence layer of the application. Once you have that working and tested, you can commit that and start working on the frontend application layer with your newly build api's. Once its finished, push and PR. What is the benefit of git add when git commit allows notes. which is helpful when you git push (the only benefit i see to get commit at this time.) You have to stage changes for commit. You might want to commit some files, but not others that you've changed. Only add the ones that you want to commit. Is this just because im working on very simple projects that finish in one sitting? Even the smallest projects can take advantage of git's robust versioning functionality, but yes, you either aren't using the functionality because you don't need to or don't know how to. More on reddit.com