Jeff Tian Jeff-Tian

Sign git commits with GPG in GitHub Actions

Generate a GPG key (see here)

gpg --full-generate-key

Save the GPG passphrase to secrets as GPG_KEY_PASSPHRASE

Example Git Branching Diagram

You can use this diagram as a template to create your own git branching diagrams. Here's how:

Create a new diagram with diagrams.net (formerly draw.io)
Go to File > Open From > URL
Insert this url (it points to the xml data below): https://gist.githubusercontent.com/bryanbraun/8c93e154a93a08794291df1fcdce6918/raw/bf563eb36c3623bb9e7e1faae349c5da802f9fed/template-data.xml
Customize as needed for your team.

How to Sign and Release to The Central Repository with GitHub Actions

GitHub allows automated builds using GitHub Actions. A commonly asked question is how to release artifacts (packaged Java jars) built by Maven and Gradle to The Central Repository. The GitHub Actions documentation provides only part of the answer.

So, first, configure your Maven project for staging artifacts to The Central Repository, by reading through Configuring Your Project for Deployment and following those steps. Please make sure that the maven-gpg-plugin is configured to prevent gpg from using PIN entry programs, as follows:

<configuration>
  <gpgArguments>
      <arg>--pinentry-mode</arg>
 loopback

Summary of book "Clean Architecture" by Robert C. Martin

Uncle Bob, the well known author of Clean Code, is coming back to us with a new book called Clean Architecture which wants to take a larger view on how to create software.

Even if Clean Code is one of the major book around OOP and code design (mainly by presenting the SOLID principles), I was not totally impressed by the book.

Clean Architecture leaves me with the same feeling, even if it's pushing the development world to do better, has some good stories and present robust principles to build software.

The book is build around 34 chapters organised in chapters.

Some Time there is a shallow update not allowed issue in your cloned GIT repo.

This means that you have to unshallow your repository. To do so you will need to add your old remote again.

git remote add origin <path-to-old-remote> After that we use git fetch to fetch the remaining history from the old remote (as suggested in this answer).

git fetch --unshallow origin And now you should be able to push into your new remote repository.

	FROM quay.io/keycloak/keycloak:17.0.0 as builder

	ENV KC_METRICS_ENABLED=true
	ENV KC_FEATURES=preview
	ENV KC_DB=postgres
	ENV KC_HTTP_RELATIVE_PATH=/auth
	# specify the custom cache config file here
	ENV KC_CACHE_CONFIG_FILE=cache-ispn-jdbc-ping.xml

	# copy the custom cache config file into the keycloak conf dir

	{
	"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
	"contentVersion": "1.0.0.0",
	"parameters": {"password": {
	"type": "securestring",
	"metadata": {
	"description": "User Password for ssh access"
	}
	},
	"vmname": {"type": "string",

	export GITHUB_USER=magickatt
	export GITHUB_TOKEN=secret
	export GITHUB_REPOSITORY=magickatt/ContainerisingLegacyApplicationsTalk
	git clone https://${GITHUB_USER}:${GITHUB_TOKEN}@github.com/${GITHUB_REPOSITORY}

	import okhttp3.*;
	import okio.Buffer;

	import javax.net.ssl.*;
	import java.io.IOException;
	import java.io.InputStream;
	import java.security.GeneralSecurityException;
	import java.security.KeyStore;
	import java.security.cert.Certificate;
	import java.security.cert.CertificateFactory;