Lalit Kale lalitkale

Pull Request Etiquette

Why do we use a Pull Request workflow?

PRs are a great way of sharing information, and can help us be aware of the changes that are occuring in our codebase. They are also an excellent way of getting peer review on the work that we do, without the cost of working in direct pairs.

Ultimately though, the primary reason we use PRs is to encourage quality in the commits that are made to our code repositories

Done well, the commits (and their attached messages) contained within tell a story to people examining the code at a later date. If we are not careful to ensure the quality of these commits, we silently lose this ability.

Login inside the container/bash into container/get inside the container []=you need to replace it with your own container/image parameter

docker run -dit [image_name]

By ID

docker exec -i -t 665b4a1e17b6 /bin/bash

By Name

docker exec -i -t loving_heisenberg /bin/bash

set the context to minikube running locally

kubectl config set-cluster minikube

create deployment yaml

kubectl run hello-world --image=myapp-container-image/k8s:1.0 --port=80 --dry-run -o yaml > myapp-deployment.yaml

create deployment yaml from existing deployment

kubectl get deployment hello-world -o yaml > my-existing-deployment.yaml

create servie yaml

Visa requirements for UK conferences.

First you'll want to check if you need a visa to enter the UK.

Nationals of the EU, Switzerland, and EEA countries will not need a visa, and are free to work and conduct business in the UK.
Nationals from some designated countries such as USA may travel for tourist or business purposes under a visa exemption. The link above will detail what documents you need to provide in order to travel under a visa exemption.
Other nationals will need a visa.

The rules for allowable business travel under a visa exemption are covered by the same rules as those travelling under a vistor visa. If you will be travelling under a visa-exemption and the conference is covering your costs in any way you should make sure to read the relevant section below.

1. Clone your fork:

git clone [email protected]:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream

	How to Write a Git Commit Message (2014) \| Hacker News
	https://news.ycombinator.com/item?id=13889155

	How to Write a Git Commit Message
	https://chris.beams.io/posts/git-commit/

	Writing good commit messages · erlang/otp Wiki
	https://github.com/erlang/otp/wiki/writing-good-commit-messages

	Commit message guidelines

	# Minikube addons
	https://github.com/kubernetes/minikube/blob/master/docs/addons.md

	#start minikube
	minikube start --vm-driver hyperv --hyperv-virtual-switch "VMVirtualSwitch" --memory 12288 --cpus 4

	#or
	minikube start --vm-driver="hyperv" --hyperv-virtual-switch="VMVirtualSwitch" --v=7 --alsologtostderr

	# minikube Patch Enviornemnt for Helm

	=== SETUP ===
	For windows clients set autocrlf to true by typing:
	$ git config --global core.autocrlf true

	For Unix/Mac
	$ git config --global core.autocrlf input

	ALSO RUN this to change all file line endings on Linux/Mac
	find . -name "*" -type f -exec dos2unix {} \;

	#!/bin/bash

	# TODO: probably accept these as CLI parameters or something
	resourceGroup='<my-resource-group>'
	cluster='<my-cluster-name>'
	region='<my-region>'

	group="MC_${resourceGroup}_${cluster}_$region"

	function wait_for_status() {

	using System;
	using System.IO;
	using System.Net;
	using System.Text;
	using System.Collections.Generic;


	public class SSEvent {
	public string Name { get; set; }
	public string Data { get; set; }