Git

2860 readers

1 users here now

Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.

Resources

Rules

Follow programming.dev rules
Be excellent to each other, no hostility towards users for any reason
No spam of tools/companies/advertisements. It’s OK to post your own stuff part of the time, but the primary use of the community should not be self-promotion.

Git Logo by Jason Long is licensed under the Creative Commons Attribution 3.0 Unported License.

founded 1 year ago

MODERATORS

Ategon

canpolat

jnovinger

Git stories (self.git)

submitted 3 months ago by canpolat to c/git

0 comments fedilink

This is a collection of posts that probe the way Git impacts our thinking and ways of working. These are exclusively discussions held within the community (and not links to blogs). Feel free to roam and join the discussion.

S3 as a Git remote and LFS server (github.com)

submitted 3 days ago by canpolat to c/git

0 comments fedilink

How to Use Git Stash to Efficiently Manage Your Code (www.freecodecamp.org)

submitted 1 week ago by canpolat to c/git

5 comments fedilink

Git 2.47 released (github.blog)

submitted 2 weeks ago by [email protected] to c/git

0 comments fedilink

Git Rev News Edition 115 (September 30th, 2024) (git.github.io)

submitted 3 weeks ago by canpolat to c/git

0 comments fedilink

A simple cheat sheet for Git (write.as)

submitted 3 weeks ago by pylapp to c/git

2 comments fedilink

git-absorb: git commit --fixup, but automatic (github.com)

submitted 3 weeks ago by canpolat to c/git

0 comments fedilink

Learn Git Branching (learngitbranching.js.org)

submitted 1 month ago by canpolat to c/git

3 comments fedilink

Radicle 1.0 released (radicle.xyz)

submitted 1 month ago by onlinepersona to c/git

0 comments fedilink

cross-posted from: https://discuss.tchncs.de/post/21810137

Radicle is an open source, peer-to-peer code collaboration stack built on Git. Unlike centralized code hosting platforms, there is no single entity controlling the network. Repositories are replicated across peers in a decentralized manner, and users are in full control of their data and workflow.

Git bisect run techniques (paperless.blog)

submitted 1 month ago by lysdexic to c/git

0 comments fedilink

Creating a Git commit: The Hard Way (avestura.dev)

submitted 1 month ago by lysdexic to c/git

0 comments fedilink

Git: avoid reset --hard, use reset --keep instead (adamj.eu)

submitted 1 month ago by norambna to c/git

8 comments fedilink

via https://fosstodon.org/@adamchainz/113069875974994637

Git Rev News Edition 114 (August 31st, 2024) (git.github.io)

submitted 1 month ago by canpolat to c/git

0 comments fedilink

PSA: Git exposes timezone metadata (sh.itjust.works)

submitted 1 month ago* (last edited 1 month ago) by [email protected] to c/git

9 comments fedilink

Git records the local timezone when a commit is made [1]. Knowledge of the timezone in which a commit was made could be used as a bit of identifying information to de-anonymize the committer.

Setting one's timezone to UTC can help mitigate this issue [2][3] (though, ofc, one must still be wary of time-of-day commit patterns being used to deduce a timezone).

References

Git documentation. git-commit. "Date Formats: Git internal format". Accessed: 2024-08-31T07:52Z. https://git-scm.com/docs/git-commit#Documentation/git-commit.txt-Gitinternalformat.

It is <unix-timestamp> <time-zone-offset>, where <unix-timestamp> is the number of seconds since the UNIX epoch. <time-zone-offset> is a positive or negative offset from UTC. For example CET (which is 1 hour ahead of UTC) is +0100.
jthill. "How can I ignore committing timezone information in my commit?". Stack Overflow. Published: 2014-05-26T16:57:37Z. (Accessed: 2024-08-31T08:27Z). https://stackoverflow.com/questions/23874208/how-can-i-ignore-committing-timezone-information-in-my-commit#comment36750060_23874208.

to set the timezone for a specific command, say e.g. TZ=UTC git commit
Oliver. "How can I ignore committing timezone information in my commit?". Stack Overflow. Published: 2022-05-22T08:56:38Z (Accessed: 2024-08-31T08:30Z). https://stackoverflow.com/a/72336094/7934600
each commit Git stores a author date and a commit date. So you have to omit the timezone for both dates.

I solved this for my self with the help of the following Git alias:
```
[alias]
co = "!f() { \
    export GIT_AUTHOR_DATE=\"$(date -u +%Y-%m-%dT%H:%M:%S%z)\"; \
    export GIT_COMMITTER_DATE=\"$(date -u +%Y-%m-%dT%H:%M:%S%z)\"; \
    git commit $@; \
    git log -n 1 --pretty=\"Autor: %an <%ae> (%ai)\"; \
    git log -n 1 --pretty=\"Committer: %cn <%ce> (%ci)\"; \
}; f"
```

Cross-posts:

git-random: build random content git trees for training purposes (git-random.olets.dev)

submitted 2 months ago by canpolat to c/git

0 comments fedilink

Store Code Discussions in Git using Git Notes (wouterj.nl)

submitted 2 months ago by canpolat to c/git

2 comments fedilink

How Does Git Store Files? (blog.git-init.com)

submitted 2 months ago by lysdexic to c/git

0 comments fedilink

Back-dating Git commits based on file modification dates (til.simonwillison.net)

submitted 2 months ago by canpolat to c/git

0 comments fedilink

Git Rev News Edition 113 (July 31st, 2024) (git.github.io)

submitted 2 months ago by canpolat to c/git

0 comments fedilink

I was wrong about git stash... - YouTube (youtube.com)

submitted 2 months ago by ruffsl to c/git

3 comments fedilink

https://git-scm.com/docs/git-worktree

Highlights from Git 2.46 (github.blog)

submitted 2 months ago by [email protected] to c/git

0 comments fedilink

vdm: A General-Purpose Versioned-Dependency Manager (GitHub) (github.com)

submitted 2 months ago by canpolat to c/git

9 comments fedilink

How I Use Git Worktrees - Alex Kladov (matklad.github.io)

submitted 2 months ago by mac to c/git

14 comments fedilink

How do you feel about storing binary files with Git? (lemmy.ca)

submitted 3 months ago by [email protected] to c/git

14 comments fedilink

I think it's generally agreed upon that large files that change often do not belong while small files that never change are fine. But there's still a lot of middle ground where the answer is not so clear to me.

So what's your stance on this? Where do you draw the line?

commit messages are optional (schpet.com)

submitted 3 months ago by mac to c/git

18 comments fedilink