See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
#include <SDL.h> | |
SDL_Window* window; | |
SDL_Renderer* renderer; | |
void drawCircle(int xc, int yc, int x, int y) { | |
SDL_RenderDrawPoint(renderer, xc + x, yc + y); | |
SDL_RenderDrawPoint(renderer, xc - x, yc + y); | |
SDL_RenderDrawPoint(renderer, xc + x, yc - y); |
# Thanks to @danger89 and @Ilothar for updating the gist. | |
# Set the name and the supported language of the project | |
project(hello-world C CXX) | |
# Set the minimum version of cmake required to build this project | |
cmake_minimum_required(VERSION 3.10) | |
# Use the package PkgConfig to detect GTK+ headers/library files | |
find_package(PkgConfig REQUIRED) | |
pkg_check_modules(GTK REQUIRED gtkmm-3.0) |
See how a minor change to your commit message style can make a difference.
Tip
Have a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs
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
#!/bin/bash | |
i=0 | |
image_i=0 | |
IMAGES_FOLDER="../images" | |
mkdir -p "$IMAGES_FOLDER" | |
TMP_HTML="../tmp.html" |
#!/bin/bash | |
files=$(grep -Eo "image_[0-9]+\.png" ./app/content/**/post.mdx) | |
for i in $files; do | |
split=$(echo $i | tr ":" "\n") | |
FILE="" | |
IMAGE="" | |
counter=0 |