Skip to content

feat: ✨ add Why Git LFS post#244

Merged
lwjohnst86 merged 7 commits intomainfrom
feat/why-git-lfs
Feb 4, 2026
Merged

feat: ✨ add Why Git LFS post#244
lwjohnst86 merged 7 commits intomainfrom
feat/why-git-lfs

Conversation

@martonvago
Copy link
Contributor

Description

This PR adds the "Why Git LFS" post.

Closes #233

Needs a thorough review.

Checklist

  • Formatted Markdown
  • Ran just run-all

@martonvago martonvago self-assigned this Jan 27, 2026
@martonvago martonvago moved this from Todo to In Review in Iteration planning Jan 27, 2026
@martonvago martonvago marked this pull request as ready for review January 27, 2026 16:02
@martonvago martonvago requested a review from a team as a code owner January 27, 2026 16:02
Copy link
Member

@signekb signekb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Very nice 👌 Some suggestions:

@github-project-automation github-project-automation bot moved this from In Review to In Progress in Iteration planning Jan 30, 2026
Copy link
Member

@lwjohnst86 lwjohnst86 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Interesting, I hadn't heard of git annex before. Nice!

martonvago and others added 5 commits February 2, 2026 09:36
Co-authored-by: Luke W. Johnston <lwjohnst86@users.noreply.github.com>
Co-authored-by: Signe Kirk Brødbæk <signebroedbaek@gmail.com>
Co-authored-by: Luke W. Johnston <lwjohnst86@users.noreply.github.com>
Co-authored-by: Signe Kirk Brødbæk <signebroedbaek@gmail.com>
@martonvago martonvago moved this from In Progress to In Review in Iteration planning Feb 2, 2026
Copy link
Member

@signekb signekb left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, two minor comments:

- The basic workflow of adding and editing data files is more complex,
because tracking the files with `git-annex` and storing the files in
a particular storage location are two distinct tasks.
- Integration with Git tooling is weaker than for Git LFS.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, ok, thanks for elaborating. You could add a sentence clarifying this.

- The basic workflow of adding and editing data files is more complex,
because separate commands have to be issued for managing data files
and code files.
- Integration with Git tooling is weaker than for Git LFS.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, does it needs it's own bullet point then, if it's about the same thing?

@github-project-automation github-project-automation bot moved this from In Review to In Progress in Iteration planning Feb 2, 2026
@martonvago martonvago moved this from In Progress to In Review in Iteration planning Feb 2, 2026
@martonvago martonvago requested a review from signekb February 2, 2026 13:39
@lwjohnst86 lwjohnst86 merged commit 92b0afb into main Feb 4, 2026
4 checks passed
@github-project-automation github-project-automation bot moved this from In Review to Done in Iteration planning Feb 4, 2026
@lwjohnst86 lwjohnst86 deleted the feat/why-git-lfs branch February 4, 2026 21:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

Why Git LFS post

3 participants