Git

2944 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

  1. Follow programming.dev rules
  2. Be excellent to each other, no hostility towards users for any reason
  3. 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 2 years ago
MODERATORS
Ategon
canpolat
jnovinger
listing: all - local
1
22
Git stories (self.git)
submitted 5 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.

2
8
Git Rev News Edition 117 (November 30th, 2024) (git.github.io)
submitted 4 weeks ago by canpolat to c/git
0 comments fedilink
3
14
Quick tip: Ignore commits in Git blame using a file (marijkeluttekes.dev)
submitted 1 month ago by canpolat to c/git
1 comments fedilink
4
13
Gitfourchette: The comfortable Git UI for Linux (github.com)
submitted 1 month ago by canpolat to c/git
0 comments fedilink
5
18
Git Commit Creation (drewdeponte.com)
submitted 1 month ago* (last edited 1 month ago) by drewdeponte to c/git
4 comments fedilink
 
 

This is an article in which I explore the details and thinking that goes into how you should create git commits, and why. I like to think of it as the article I wish existed when I was just starting out over 20 years ago.

I wanted to cover all the things that you should think about at a high level. That way it at least could work as an entry point to deeper exploration of the particular areas if the reader isn’t completely sold or they want to just gain a deeper understanding. While at the same time trying to provide enough details to show why and how these choices are valuable. This is always a tricky balance.

Anyways, I would love any feedback on thoughts on how this could be improved.

Thanks

6
23
Mergiraf: a syntax-aware merge driver for Git (mergiraf.org)
submitted 1 month ago by canpolat to c/git
0 comments fedilink
7
10
Git Rev News Edition 116 (October 31st, 2024) (git.github.io)
submitted 1 month ago by canpolat to c/git
0 comments fedilink
8
16
S3 as a Git remote and LFS server (github.com)
submitted 2 months ago by canpolat to c/git
0 comments fedilink
9
15
How to Use Git Stash to Efficiently Manage Your Code (www.freecodecamp.org)
submitted 2 months ago by canpolat to c/git
5 comments fedilink
10
17
Git 2.47 released (github.blog)
submitted 2 months ago by [email protected] to c/git
0 comments fedilink
11
6
Git Rev News Edition 115 (September 30th, 2024) (git.github.io)
submitted 2 months ago by canpolat to c/git
0 comments fedilink
12
14
A simple cheat sheet for Git (write.as)
submitted 3 months ago by pylapp to c/git
2 comments fedilink
13
12
git-absorb: git commit --fixup, but automatic (github.com)
submitted 3 months ago by canpolat to c/git
0 comments fedilink
14
27
Learn Git Branching (learngitbranching.js.org)
submitted 3 months ago by canpolat to c/git
3 comments fedilink
15
7
Radicle 1.0 released (radicle.xyz)
submitted 3 months 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.

16
11
Git bisect run techniques (paperless.blog)
submitted 3 months ago by lysdexic to c/git
0 comments fedilink
17
29
Creating a Git commit: The Hard Way (avestura.dev)
submitted 3 months ago by lysdexic to c/git
0 comments fedilink
18
56
Git: avoid reset --hard, use reset --keep instead (adamj.eu)
submitted 3 months ago by norambna to c/git
8 comments fedilink
 
 

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

19
3
Git Rev News Edition 114 (August 31st, 2024) (git.github.io)
submitted 3 months ago by canpolat to c/git
0 comments fedilink
20
41
PSA: Git exposes timezone metadata (sh.itjust.works)
submitted 4 months ago* (last edited 4 months 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

  1. 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.

  2. 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

  3. 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:

21
21
git-random: build random content git trees for training purposes (git-random.olets.dev)
submitted 4 months ago by canpolat to c/git
0 comments fedilink
22
31
Store Code Discussions in Git using Git Notes (wouterj.nl)
submitted 4 months ago by canpolat to c/git
2 comments fedilink
23
24
How Does Git Store Files? (blog.git-init.com)
submitted 4 months ago by lysdexic to c/git
0 comments fedilink
24
28
Back-dating Git commits based on file modification dates (til.simonwillison.net)
submitted 4 months ago by canpolat to c/git
0 comments fedilink
25
8
Git Rev News Edition 113 (July 31st, 2024) (git.github.io)
submitted 5 months ago by canpolat to c/git
0 comments fedilink
view more: next ›