See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope>
is optional
#!/usr/bin/env python | |
# Tutorial available at: https://www.youtube.com/watch?v=uSt80abcmJs | |
# Feedback welcome: [email protected] | |
from gimpfu import * | |
def extreme_unsharp_desaturation(image, drawable): | |
pdb.gimp_image_undo_group_start(image) | |
radius = 5.0 |
[vsc] | |
definition-foreground = #3987d6 | |
error-foreground = #fe1b1b | |
normal-foreground = #dcdcdc | |
keyword-foreground = #3987d6 | |
hilite-foreground = #dcdcdc | |
comment-background = #1e1e1e | |
hit-foreground = #ffffff | |
builtin-background = #1e1e1e | |
stdout-foreground = #dcdcdc |
You can use this diagram as a template to create your own git branching diagrams. Here's how:
https://gist.githubusercontent.com/bryanbraun/8c93e154a93a08794291df1fcdce6918/raw/bf563eb36c3623bb9e7e1faae349c5da802f9fed/template-data.xml
feat: new feature
fix(scope): bug in scope
feat!: breaking change
/ feat(scope)!: rework API
chore(deps): update dependencies
build
: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)ci
: Changes to CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)chore
: Changes which doesn't change source code or tests e.g. changes to the build process, auxiliary tools, librariesThis downloads standalone 64-bit MSVC compiler, linker & other tools, also headers/libraries from Windows SDK into portable folder, without installing Visual Studio. Has bare minimum components - no UWP/Store/WindowsRT stuff, just files & tools for 64-bit native desktop app development.
Run python.exe portable-msvc.py
and it will download output into msvc
folder. By default it will download latest available MSVC & Windows SDK - currently v14.32.17.2 and v10.0.22621.0.
You can list available versions with python.exe portable-msvc.py --show-versions
and then pass versions you want with --msvc-version
and --sdk-version
arguments.
To use cl.exe/link.exe from output folder, first run setup.bat
- after that PATH/INCLUDE/LIB env variables will be setup to use all the tools as usual. You can also use clang-cl.exe with these includes & libraries.
To use clang-cl.exe without running setup.bat, pass extra /winsysroot msvc
argument (msvc is folder name where output is stored).