ggordonutech

# Utilize the docker container image tagged as "maven:latest"
# see - https://hub.docker.com/_/maven
# What is a container - https://www.docker.com/resources/what-container
image: maven:latest

# We now specify the differnt stages of our CI build. We have 3 stages
stages:
  - build
  - test
  - package

iwanbolzern

image: docker:latest
services:
    - docker:dind
stages:
    - Dev
    - Dev-publish
    - Prod-Tag
    - Prod-publish
variables:
    REGISTRY: [Your Registry]

calebporzio

details summary {
  cursor: pointer;
  outline: none !important;
  display: inline-block;
  padding: 8px 12px;
  padding-top: 10px;
  border-radius: 4px;
  overflow: hidden;
  background: #F09825;
  color: white;

dmstern

# located in .git/config:
# VSCode will use this to prefill the git commit message box.
[commit]
	template = .git/.gitmessage.txt

jsyi

#!/bin/bash

cd ${bamboo.build.working.directory}
REPO_URL=${bamboo.planRepository.1.repositoryUrl} 
[[ $REPO_URL =~ github.com\/(.*).git ]]
STATUS_UPDATE_URL="https://api.github.com/repos/${BASH_REMATCH[1]}/statuses/${bamboo.repository.revision.number}"

if ls **/test-reports/*.xml 1> /dev/null 2>&1; then
  curl -H "Authorization: token ${bamboo.githubStatusUpdateTokenForMeshkoreaDev}" --request POST --data '{"state": "success", "context": "bamboo/build", "description": "Bamboo build Completed!", "target_url": "${bamboo.buildResultsUrl}"}' $STATUS_UPDATE_URL > /dev/null
else

bsara

Setup SSH Authentication for Git Bash on Windows

Prepararation

0. Create a folder at the root of your user home folder (Example: C:/Users/uname/) called .ssh.
1. Create the following files if they do not already exist (paths begin from the root of your user home folder):

• .ssh/config

stowball

$z-indexes: (
    main: (
        above-inherit: (),
        nested: (
            low,
            middle,
            high
        ),
        tooltip: ()
    ),

JamieMason

a, abbr, acronym, address, applet, area, article, aside, audio, b, base,
basefont, bdi, bdo, bgsound, big, blink, blockquote, body, br, button, canvas,
caption, center, cite, code, col, colgroup, content, data, datalist, dd, del,
details, dfn, dir, div, dl, dt, em, embed, fieldset, figcaption, figure, font,
footer, form, frame, frameset, h1, h2, h3, h4, h5, h6, head, header, hgroup, hr,
html, i, iframe, img, input, ins, isindex, kbd, keygen, label, legend, li, link,
listing, main, map, mark, marquee, menu, menuitem, meta, meter, nav, nobr,
noframes, noscript, object, ol, optgroup, option, output, p, param, plaintext,
pre, progress, q, rp, rt, ruby, s, samp, script, section, select, shadow, small,
source, spacer, span, strike, strong, style, sub, summary, sup, table, tbody,

amirsuhail786

	" Make IE Better Compatible "

<!--[if IE]>
<script src="http://html5shim.googlecode.com/svn/trunk/html5.js"></script>
<![endif]-->

======================================================
IE6 Only
==================
_selector {...}

adactio

<h1>Standardisation</h1>
There was not a lot of discussion of this at <a href=Introduction.html>ECHT90</a>, but there seem to be two leads:
<ol>
<li><a href=People.html#newcombe>Steve newcombe's</a> and Goldfarber's "Hytime" committee
looking into SGML, and
<li>An ISO working group known as MHEG, "Multimedia/HyperText Expert Group".
led by one Francis Kretz (Thompsa SA? Rennes?).
</lo>