skylock

version: '3.4'

services:
  db:
    image: "mcr.microsoft.com/mssql/server:2017-latest"
    container_name: "monetoplus-mssql"
    ports:
      - "1433:1433"
    environment:
      SA_PASSWORD: "Pass@word"

skylock

import {FormGroup, ValidationErrors} from '@angular/forms';

export interface IFormError {
  control: string;
  error: string;
  value: any;
}

export function getFormValidationErrors(form: FormGroup) {
  const result = [];

skylock

version: '3.4'

services:
  db:
    image: "mcr.microsoft.com/mssql/server:2017-latest"
    container_name: "monetoplus-mssql"
    ports:
        - "1433:1433"
    environment:
        SA_PASSWORD: "Pass@word"

skylock

services:
  https-portal:
    image: steveltn/https-portal:1
    ports:
      - '80:80'
      - '443:443'
    restart: always
    environment:
      DOMAINS: 'jenkins.monetoplus.com -> http://jenkins:8080'
      #STAGE: 'production' # Don't use production until staging works

skylock

Conventional Commit Messages

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 and generate verion and changelogs

Commit Message Formats

Default

skylock

.DEFAULT_GOAL := help

# VARIABLES

# TARGETS

# See details at from http://marmelab.com/blog/2016/02/29/auto-documented-makefile.html
help: ## Prints this help message
	@grep -E '^[a-zA-Z_-]+:.*?## .*$$' $(MAKEFILE_LIST) | awk 'BEGIN {FS = ":.*?## "}; {printf "\033[36m%-30s\033[0m %s\n", $$1, $$2}'

skylock

Git Commit Messages Style-Guides

• Use the present tense ("Add feature" not "Added feature")
• Use the imperative mood ("Move cursor to..." not "Moves cursor to...")
• Limit the first line to 72 characters or less
• Reference issues and pull requests liberally after the first line
• When only changing documentation, include [ci skip] in the commit title
• Consider starting the commit message with an applicable emoji

Types

skylock

With the introduction of GitHub's Squash and Merge feature, this has become less prevelant, however it's still useful in scenarios where GitHub's interface is unavailable.

Let's talk through two ways to do a squash and merge on the command line.

Take 1: Interactive Rebase

When to use it

• When you have not merged main into your feature branch
• There are no merge conflicts

skylock

People

:bowtie:	😄 :smile:	😆 :laughing:
😊 :blush:	😃 :smiley:	☺️ :relaxed:
😏 :smirk:	😍 :heart_eyes:	😘 :kissing_heart:
😚 :kissing_closed_eyes:	😳 :flushed:	😌 :relieved:
😆 :satisfied:	😁 :grin:	😉 :wink:
😜 :stuck_out_tongue_winking_eye:	😝 :stuck_out_tongue_closed_eyes:	😀 :grinning:
😗 :kissing:	😙 :kissing_smiling_eyes:	😛 :stuck_out_tongue:

skylock

Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.

Format: <type>(<scope>): <subject>

<scope> is optional

Example