The Wiert Corner – irregular stream of stuff

Jeroen W. Pluimers on .NET, C#, Delphi, databases, and personal interests

  • My badges

  • Twitter Updates

    • RT @NodeSpace: Due to IPv4 shortages and the world refusing to use IPv6, we’re moving all services to IPX/SPX. After all, 0BAD33CE:0003FE7C… 1 hour ago
    • RT @Visit_NL: We're proud to present the ultimate Dutch flower: the #FloresTouristia! See for yourself how our scientists have worked mirac… 1 hour ago
    • RT @HPN2_0: Yep. That sums it up quite nicely. 1 hour ago
    • RT @adestmusica: Presentatie nieuwe uniformen! 🤩💂 Zaterdag 15 april is “Adest-dag” want deze middag zal de Drum- en Showband hun nieuwe un… 2 hours ago
    • @matijn Het goede nieuws is een nieuw huis. Mooi hoor! 2 hours ago
  • My Flickr Stream

  • Pages

  • All categories

  • Enter your email address to subscribe to this blog and receive notifications of new posts by email.

    Join 4,182 other subscribers

Archive for the ‘Source Code Management’ Category

git add a revision before first commit – Google Search

Posted by jpluimers on 2023/03/21

Will need this one day to gain better insight on how git works under the hood: [Wayback/Archive] git add a revision before first commit – Google Search

–jeroen

Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »

A pain in the ass: gist include image in markdown in current directory – Google Search

Posted by jpluimers on 2023/03/08

This revealed so much pain: [Wayback] gist include image in markdown in current directory – Google Search

I wished that – like in the past – it would work just like in a normal github hosted git repository: [Wayback/Archive] How do I display local image in markdown? – Stack Overflow.

The core problem is that though a gist underneath is a git repository, it is rendered in a way that is different than a github repository is rendered, and that way of rendering has changed over the years effectively making it difficult to embed a picture. When you do embed an image requires the uuid/guid of the raw image URL to be included in the markdown, unlike with a regular repository hosted on github.

That is so much pain that I decided to not host documentation in gists any more.

A bit of the pain:

This is an example gist where I tried to host an image: [Wayback/Archive] Windows 7 with PowerShell v2 fails to upgrade to PowerShell v3 through chocolatey: You must provide a value expression on the right-hand side of the '-' operator.

That gist was prelude to my post Chocolatey on Windows 7: “You must provide a value expression on the right-hand side of the ‘-‘ operator.”.

–jeroen

Posted in Development, DVCS - Distributed Version Control, gist, git, GitHub, Lightweight markup language, MarkDown, Software Development, Source Code Management | Leave a Comment »

Learning github actions by creating a repository with a dynamic README.md for your profile information

Posted by jpluimers on 2023/01/23

TL;DR:

  1. Create a GitHub repository with the same name as your profile name
  2. Add a README.md with Markdown describing your profile
  3. In the README.md, add begin/end HTML comment markers <!-- and --> for various types of dynamic content
  4. In the Actions of this repository, add Workflows for each of the set comment markers that use them to refresh that part of the content using GitHub Actions learning some continuous integration/continuousc deployment (CI/CD) on the fly.

You can spice this up with all kinds of badges to make it look pretty.

HTML Comments in Markdown?

Yes, it is indeed odd to have HTML comments in Markdown where you could just as easy use Markdown comments, but hey: I didn’t define the way this works.

A Markdown comment looks like this:

(empty line)
[comment]: # (This actually is the most platform independent comment)

For explanation on why/how this works, see the below two great StackOverflow answers in this order:

  1. [Wayback/Archive] syntax – Comments in Markdown: concise example – Stack Overflow by [Wayback/Archive] Magnus.
  2. [Wayback/Archive] syntax – Comments in Markdown: explainer – Stack Overflow by [Wayback/Archive] User Nick Volynkin – Stack Overflow

Howto

The below two videos (also embedded below the signature) show how to do this. Thanks [Archive] Jesse Hall 🦸‍♂️ #vsCodeHero (@codeSTACKr) | Twitter for creating them!

  1. [Wayback/Archive] Next Level GitHub Profile README (NEW) | How To Create An Amazing Profile ReadMe With GitHub Actions – YouTube
  2. [Wayback/Archive] UPDATE: Next Level GitHub Profile README (NEW) | GitHub Actions | Vercel | Spotify – YouTube

The description of the videos contain all sorts of links to sites and underlying repositories for:

  • icons
  • shields
  • badges
  • youtube/blog/RSS and other feed actions
  • profile examples

You can see the effects at [Wayback/Archive] codeSTACKr/codeSTACKr in the [Wayback/Archive] raw README.md sources.

Enough to get you some experimentation (:

Watch your commits

One of the drawbacks of mixing manual and automated changes to a repository, is that the automated changes can cause a lot of commits.

This is OK as long as the automated changes add value to the changed content.

In this regard, having stable RSS feeds is important, and YouTube is kind of bad at this when you look at [Wayback/Archive] History for README.md – codeSTACKr/codeSTACKr: videos changing order or popping in/out of the last 5 is kind of annoying.

–jeroen

Read the rest of this entry »

Posted in Development, DVCS - Distributed Version Control, git, GitHub, GitHub Actions, Lightweight markup language, MarkDown, Power User, Source Code Management | Leave a Comment »

Some experience of htmlpreview.github.io as a replacement for rawgit.com

Posted by jpluimers on 2022/12/01

With [Wayback/Archive] rawgit.com having sunset years ago, but still having a [Wayback/Archive] few links to it from my blog, it was time to take a closer look at the alternative [Wayback/Archive] htmlpreview.github.io.

First of all, htmlpreview needs more examples. I might submit a pull request for it later, as it is open source at [Archive/Archive] htmlpreview/htmlpreview.github.com: HTML Preview for GitHub Repositories.

Second, some actual example URLs, based on content I previously accessed through rawgit.com.

Read the rest of this entry »

Posted in Development, DVCS - Distributed Version Control, git, GitHub, HTML, Power User, rawgit, Software Development, Source Code Management, Versioning, Web Development | Leave a Comment »

Git (even recent versions) hanging after “Resolving deltas: 100%”

Posted by jpluimers on 2022/09/29

If you ever come across git hanging after completing “Resolving deltas: 100%“, then remember this can still happen with recent git versions; the below output was with git version 2.24.1.windows.2.

C:\bin>git clone https://wiert@gitlab.com/wiert.me/private/Windows/bin.git
Cloning into 'bin'...
remote: Enumerating objects: 74, done.
remote: Counting objects: 100% (74/74), done.
remote: Compressing objects: 100% (54/54), done.
remote: Total 1063 (delta 30), reused 39 (delta 15)
Receiving objects: 100% (1063/1063), 26.74 MiB | 516.00 KiB/s, done.
Resolving deltas: 100% (385/385), done.

or (after pressing Ctrl-C):

C:\bin>git clone https://wiert@gitlab.com/wiert.me/private/Windows/bin.git
Cloning into 'bin'...
remote: Enumerating objects: 74, done.
remote: Counting objects: 100% (74/74), done.
remote: Compressing objects: 100% (54/54), done.
remote: Total 1063 (delta 30), reused 39 (delta 15)
Receiving objects: 100% (1063/1063), 26.74 MiB | 516.00 KiB/s, done.
Resolving deltas: 100% (385/385), done.
fatal: index-pack failed

Retry after a while

Sometimes this is as easy as waiting until the remote system comes to its senses. In this case, waiting some 8 hours resolved it:

C:\bin>git clone https://wiert@gitlab.com/wiert.me/private/Windows/bin.git
C:\bin>git clone https://wiert@gitlab.com/wiert.me/private/Windows/bin.git
Cloning into 'bin'...
remote: Enumerating objects: 74, done.
remote: Counting objects: 100% (74/74), done.
remote: Compressing objects: 100% (54/54), done.
remote: Total 1063 (delta 30), reused 39 (delta 15)
Receiving objects: 100% (1063/1063), 26.74 MiB | 748.00 KiB/s, done.
Resolving deltas: 100% (385/385), done.

In my case this worked, even though GitLab did not show any problems in their status history: [WayBack] GitLab System Status History.

I waited (and succeeded) because of [WayBack] git – How to solve’fatal: index-pack failed’? – Stack Overflow.

Check the index and get the most recent

Some links that I want to check out later:

Searches

–jeroen

Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »

 
%d bloggers like this: