You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: rev_news/drafts/edition-113.md
+138-2Lines changed: 138 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -129,15 +129,151 @@ This edition covers what happened during the months of June 2024 and July 2024.
129
129
130
130
__Various__
131
131
132
+
+[Highlights from Git 2.46](https://github.blog/open-source/git/highlights-from-git-2-46/)
133
+
Taylor Blau on GitHub Blog. Those include pseudo-merge reachability bitmaps,
134
+
subcommands in [git-config](https://git-scm.com/docs/git-config/2.46.0) (like `git config list`),
135
+
enhanced credential helper protocol, and improving though still experrimental reftable support.
136
+
+[Anyone can Access Deleted and Private Repository Data on GitHub](https://trufflesecurity.com/blog/anyone-can-access-deleted-and-private-repo-data-github)
137
+
via Cross Fork Object Reference (CFOR) from another [public] fork.
138
+
Any code committed to a public repository may be accessible forever
139
+
as long as there is at least one public fork of that repository.
140
+
This is intentional design decision by GitHub; see [the documentation](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/what-happens-to-forks-when-a-repository-is-deleted-or-changes-visibility).
141
+
There is though a separate fork network for public and for private versions
142
+
of the same repository.<br>
143
+
Posted on Truffle Security blog.
144
+
+[Debian debate over tag2upload reaches compromise](https://lwn.net/Articles/978324/)
145
+
by Joe Brockmeier on LWN\.net. The [tag2upload service](https://salsa.debian.org/dgit-team/dgit/-/blob/master/TAG2UPLOAD-DESIGN.txt)
146
+
promises a streamlined way for Debian developers using Git to upload packages to
147
+
the [Debian Archive](https://wiki.debian.org/Services/Debian%20Archive).
148
+
132
149
133
150
__Light reading__
134
151
135
-
<!---
152
+
+[A Git story: Not so fun this time](https://blog.brachiosoft.com/en/posts/git/)
153
+
on Brachiosoft Blog. The title refers to the ["Just for Fun"](https://www.amazon.com/Just-Fun-Story-Accidental-Revolutionary/dp/0066620732/)
154
+
book, the 2001 autobiography of Linux kernel creator Linus Torvalds,
155
+
and how Git origin story wasn't so much fun, at least for Linus.
156
+
The article provides list of references. Includes new material
157
+
not seen in earlier retelling of the Git history, like the ones linked in
158
+
[Git Rev News Edition #2](https://git.github.io/rev_news/2015/04/05/edition-2/) (on 10 years of Git),
and [Edition #112](https://git.github.io/rev_news/2024/06/30/edition-112/)
163
+
(among others).
164
+
+[Pull requests via git push](https://blog.sesse.net/blog/tech/2024-07-15-13-04_pull_requests_via_git_push.html)
165
+
and a specially crafted `pre-receive` hook (and `git-http-backend` configured
166
+
to allow anonymous push) that turns `git push` into series of patch emails.
167
+
(Though this approach has some limitations.) Written by Steinar H. Gunderson on his blog.
168
+
+ See also [git-pr](https://pr.pico.sh/) in "Git tools and sites" section.
169
+
+[How I Use Git Worktrees](https://matklad.github.io/2024/07/25/git-worktrees.html)
170
+
by Alex Kladov (matklad) on his GitHub Pages-based blog.
171
+
TL;DR: consider using worktrees not as a replacement for branches,
172
+
but as a means to manage concurrency in your tasks (for example: view, work, review, fuzz, scratch).
173
+
+[Git autocorrect needs more marketing](https://dev.to/cloudx/git-autocorrect-needs-more-marketing-20gg)
174
+
by Axel Navarro for Cloud(x); on DEV\.to.
175
+
+[commit messages are optional](https://schpet.com/note/git-commit-messages-are-optional)
176
+
by Peter Schilling in schpet’s notebook (though for some of mentioned uses,
177
+
commits with empty commit messages are better replaced with `git commit --fixup`).
178
+
+[Git-ifying SVN: How I Brought Modern Version Control to an Age-Old System](https://ionixjunior.dev/en/gitifying-svn-how-i-brought-modern-version-control-to-an-ageold-system/)
179
+
by Ione Souza Junior on his blog; also available [on DEV.to](https://dev.to/ionixjunior/git-ifying-svn-how-i-brought-modern-version-control-to-an-age-old-system-4o3e)
180
+
as a last part of the [mastering-git series](https://dev.to/ionixjunior/series/26070).
181
+
Another article from this series was mentioned in [Git Rev News Edition #112](https://git.github.io/rev_news/2024/06/30/edition-112/).
182
+
+[Benchmarking the Modern Development Experience across Versioning Tools: S3, DVC, Git LFS, and XetHub](https://about.xethub.com/blog/benchmarking-the-modern-development-experience)
183
+
by Ann Huang on XetHub blog.
184
+
+[XetHub](https://about.xethub.com/) is development platform for datasets and models,
185
+
which automatically versions and tracks assets across the Machine Learning stack
186
+
to guarantee reproducibility. Mentioned in passing in [Git Rev News Edition #95](https://git.github.io/rev_news/2023/01/31/edition-95/) news.
187
+
+ The comparison does not include [DagsHub's Direct Data Access / Data Streaming](https://dagshub.com/docs/feature_guide/dagshub_storage/data_streaming/),
188
+
which was [announced](https://dagshub.com/blog/launching-data-streaming-and-upload/) in 2022.
189
+
[DagsHub](https://dagshub.com/), a web platform for storing, versioning and managing data (data hub),
190
+
was first mentioned in [Git Rev News Edition #72](https://git.github.io/rev_news/2021/02/27/edition-72/)
191
+
+[The visualization and analysis of git commit statistics for IT team leaders.](https://dev.to/responsivecrocodile/the-visualization-and-analysis-of-git-commit-statistics-for-it-team-leaders-2pof)
192
+
by Aleksei Bakhirev (Responsive Crocodile) on DEV\.to. Uses the [Assayo](https://github.com/bakhirev/assayo)
193
+
tool written by the author for plots (see also the [assayo.online](https://assayo.online/) webpage).
194
+
+[Reorient GitHub Pull Requests Around Changesets](https://mitchellh.com/writing/github-changesets)
195
+
from one giant mutable changeset, by Mitchell Hashimoto on his blog (2023).
196
+
+[A Note About Git Commit Messages](https://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html)
197
+
(2008) by Tim Pope on tbaggery blog; it also explains some of reasoning behind recommendations.
198
+
199
+
200
+
201
+
202
+
+ git good (My Hero Academia fanfiction, humor/horror) - Izuku's quirk is Git,
203
+
the version control software (some artistic license taken in order to make a good story).
204
+
By Unknownlight. Available [on Archive of Our Own](https://archiveofourown.org/works/55773742/chapters/141591955),
205
+
[on FanFiction.net](https://www.fanfiction.net/s/14369888/1/git-good) (not recommended by the author),
206
+
and [on SpaceBattles](https://forums.spacebattles.com/threads/git-good-my-hero-academia-izukus-quirk-is-git-the-version-control-software.1163142/).<br>
207
+
Summary:
208
+
> Reality shattered like broken glass. The firmament that separated the real world from the eldritch beyond had broken. Two timelines had collided in the center of the street—an incongruous synthesis of two different chains of events. A building collapsed, and it did not. An explosion devastated the surroundings, and it did not. Screaming faces and laughs of joy overlapped each other as if viewed through a kaleidoscopic prism.
209
+
>
210
+
> The crowd looked on in horror and awe. Who was responsible for tearing apart the fabric of reality?
211
+
>
212
+
> Izuku groaned. _'Great, another merge conflict'_, he thought. _'What a pain'_.
213
+
214
+
136
215
__Easy watching__
137
-
-->
216
+
217
+
+[I was wrong about `git stash`...](https://www.youtube.com/watch?v=ntM7utSjeVU)
218
+
(or rather, how one can use `git worktree`), by Philomatics on YouTube [5:18].
219
+
138
220
139
221
__Git tools and sites__
140
222
223
+
+[pico/git-pr](https://pr.pico.sh/) (Patch Requests) is a new Git collaboration service,
224
+
where you send and retrieve patches not via email but via SSH to a `git-pr` server:
225
+
```bash
226
+
# Contributor submits his/her changes:
227
+
git format-patch origin/main --stdout | ssh pr.pico.sh pr create test
228
+
# > Patch Request has been created (ID: 1)
229
+
230
+
# Owner can apply those changes via patch request:
231
+
ssh pr.pico.sh pr print 1 | git am -3
232
+
```
233
+
Can be self-hosted. Written in Go, MIT licensed.
234
+
+[eza](https://github.com/eza-community/eza) is a modern replacement
235
+
for the venerable file-listing command-line program `ls`. It knows about symlinks,
236
+
extended attributes, and Git (like file status in Git repo, Git repo status,
237
+
or ignoring files mentioned in `.gitignore`). Written in Rust, MIT licensed.
238
+
See the [documentation](https://eza.rocks/).
239
+
+[BlenderBIM](https://blenderbim.org/) is an add-on for detailed and
0 commit comments