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: _posts/2020-11-27-edition-69.markdown
+59-51Lines changed: 59 additions & 51 deletions
Original file line number
Diff line number
Diff line change
@@ -196,55 +196,60 @@ This edition covers what happened during the month of October 2020.
196
196
__Various__
197
197
198
198
*[Announcing the Release of the Git Experience in Visual Studio](https://devblogs.microsoft.com/visualstudio/announcing-the-release-of-the-git-experience-in-visual-studio/);
199
-
the new Git tooling is now the default source control experience
200
-
in Visual Studio 2019, beginning with [version 16.8](https://devblogs.microsoft.com/visualstudio/visual-studio-2019-v16-8/#git-productivity).
201
-
* Kernel.org manager Konstantin Ryabitsev announced that [signed git pushes](https://people.kernel.org/monsieuricon/signed-git-pushes)
202
-
are now supported by the kernel.org system. Among other things, push signatures
203
-
can be preserved in a commit transparency log, [which is also now provided](https://people.kernel.org/monsieuricon/introducing-the-kernel-org-git-transparency-log)
204
-
by kernel.org.
205
-
199
+
the new Git tooling is now the default source control experience
are now supported by the kernel.org system. Among other things, push signatures
205
+
can be preserved in a commit transparency log,
206
+
[which is also now provided](https://people.kernel.org/monsieuricon/introducing-the-kernel-org-git-transparency-log)
207
+
by kernel.org.
206
208
207
209
__Light reading__
208
210
209
211
*[Git before GitHub](https://tarunbatra.com/blog/x/git-before-github/)
210
-
by Tarun Batra is a beginner-friendly article explaining how to submit
211
-
patches using git's built-in tools without using a platform like GitHub.
212
+
by Tarun Batra is a beginner-friendly article explaining how to submit
213
+
patches using git's built-in tools without using a platform like GitHub.
212
214
*[How to keep your Git history clean with interactive rebase](https://about.gitlab.com/blog/2020/11/23/keep-git-history-clean-with-interactive-rebase/)
213
-
by Tobias Günther on GitLab Blog. Interactive rebase is one of Git's
214
-
most versatile tools. Here's how to use it to correct commit messages,
215
-
fix mistakes, and more.
215
+
by Tobias Günther on GitLab Blog. Interactive rebase is one of Git's
216
+
most versatile tools. Here's how to use it to correct commit messages,
217
+
fix mistakes, and more.
216
218
*[How I remember everything I learn](https://aurelio.me/blog/How-I-remember-everything-I-learn/) by Aurelio Ogliari; he uses [his personal wiki](https://github.com/nobitagit/knowledge),
217
-
which is nothing more than a Git repo (on GitHub), divided in folders
218
-
with a bunch of READMEs in each of them.
219
+
which is nothing more than a Git repo (on GitHub), divided in folders
220
+
with a bunch of READMEs in each of them.
219
221
*[GitHub Actions for semi-static web sites](https://dev.to/davorg/github-actions-for-semi-static-web-sites-597g)
220
-
by Dave Cross on Dev.To explains how to keep a site up-to-date where
221
-
there are only a few ways that it can change, like [CPAN Dashboard](https://cpandashboard.com/).
222
-
([GitHub Actions](https://github.com/features/actions), then beta,
223
-
were covered in [Git Rev News #44](https://git.github.io/rev_news/2018/10/24/edition-44/)).
222
+
by Dave Cross on Dev.To explains how to keep a site up-to-date where
223
+
there are only a few ways that it can change, like [CPAN Dashboard](https://cpandashboard.com/).
224
+
([GitHub Actions](https://github.com/features/actions), then beta,
225
+
were covered in [Git Rev News #44](https://git.github.io/rev_news/2018/10/24/edition-44/)).
224
226
*[What adding CI to 30 projects revealed](https://dev.to/szabgab/what-adding-ci-to-30-projects-revealed-3d4k)
225
-
by Gabor Szabo on Dev.To. Among others it found developer forgetting to add
226
-
file to Git repository, or pushing some changes, or that build script depends
227
-
on unreleased code or local configuration, or that not all dependencies were
228
-
declared.
229
-
*[Nbdev: A literate programming environment that democratizes software
230
-
engineering best practices](https://github.blog/2020-11-20-nbdev-a-literate-programming-environment-that-democratizes-software-engineering-best-practices/)
231
-
by Hamel Husain on GitHub Blog. [nbdev](https://nbdev.fast.ai/) builds
232
-
on top of Jupyter notebooks to encompass the entire software development
233
-
life cycle: automated generation of docs, Continuous Integration (CI),
234
-
writing tests directly in notebooks, etc. Many of those features are
235
-
integrated with GitHub (GitHub Actions, GitHub Pages, GitHub Codespaces).
227
+
by Gabor Szabo on Dev.To. Among others it found developer forgetting to add
228
+
file to Git repository, or pushing some changes, or that build script depends
229
+
on unreleased code or local configuration, or that not all dependencies were
230
+
declared.
231
+
*[Nbdev: A literate programming environment that democratizes software engineering best practices](https://github.blog/2020-11-20-nbdev-a-literate-programming-environment-that-democratizes-software-engineering-best-practices/)
232
+
by Hamel Husain on GitHub Blog. (See also nbdev's mention in the 'Git
233
+
tools and sites' section below.) [nbdev](https://nbdev.fast.ai/)
234
+
builds on top of Jupyter notebooks to encompass the entire software
235
+
development life cycle: automated generation of docs, Continuous
236
+
Integration (CI), writing tests directly in notebooks, etc. Many of
237
+
those features are integrated with GitHub (GitHub Actions, GitHub
238
+
Pages, GitHub Codespaces).
236
239
*[Git is simply too hard](https://changelog.com/posts/git-is-simply-too-hard):
237
-
a fancified excerpt of Mislav Marohnić's unpopular opinion on [Go Time #153](https://changelog.com/gotime/153)
238
-
podcast.
239
-
See also [Gitless](https://gitless.com/), the experimental reworking of Git,
240
-
based on [research on difficulties in Git](https://gitless.com/#research),
241
-
mentioned in [Git Rev News #20](https://git.github.io/rev_news/2016/10/19/edition-20/).
240
+
a fancified excerpt of Mislav Marohnić's unpopular opinion on [Go Time #153](https://changelog.com/gotime/153)
241
+
podcast. See also [Gitless](https://gitless.com/), the experimental reworking of Git,
242
+
based on [research on difficulties in Git](https://gitless.com/#research),
243
+
mentioned in [Git Rev News #20](https://git.github.io/rev_news/2016/10/19/edition-20/).
242
244
* Gerrit Code Review fixes two important security vulnerabilities,
243
-
[Issue 13621](https://bugs.chromium.org/p/gerrit/issues/detail?id=13621) and [Issue 13514](https://bugs.chromium.org/p/gerrit/issues/detail?id=13514).
244
-
They have been found during the test migrations of the [OpenDev Code Review service](https://review.opendev.org/) to the latest version v3.2.
245
-
The issue was particularly sensitive for all those setups hosted in Europe, because of
246
-
the potential exposure to other people's personal information, such as e-mail and external ids,
247
-
and was impacting only those very old setups that had recently migrated to v2.14 or later.
245
+
[Issue 13621](https://bugs.chromium.org/p/gerrit/issues/detail?id=13621) and
0 commit comments