Skip to content

Release posts: Add Gitaly's contributions to Git in 2.45

John Cai requested to merge jc/git-2.45-release into master

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

The Gitaly team contributes heavily to the Git project, which benefits GitLab and its users under the hood with improvements to Git. These improvements however, are often unnoticed as they happen apart from the GitLab ecosystem on the Git mailing list. As a way to bridge the communication gap, let's add a few highlights from https://about.gitlab.com/blog/2024/04/30/whats-new-in-git-2-45-0/ to the release post. Even though these contributions to Git are not directly to GitLab, the downstream effects of these contributions definitely are interesting to our customers.

More context in gitlab-org/core-platform-section/discussions#151 (comment 1797740885) with the decision to add Git work to a release post every 3 months.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

  • Provided a concise title for this Merge Request (MR)
  • Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
    • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added, and the content is SAFE
  • Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
    • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
    • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
    • The when to get approval handbook section explains the workflow in more detail
  • For transparency, share this MR with the audience that will be impacted.
    • Team: For changes that affect your direct team, share in your group Slack channel
    • Department: If the update affects your department, share the MR in your department Slack channel
    • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR

Commits

  • Release posts: Add Gitaly's contributions to Git in 2.45
Edited by John Cai

Merge request reports