eliranmal

GitLab MR links check

how to test for broken links on incoming changes to the codebase (and not only validite URL syntax).

TL;DR

replace <1234> with the desired MR number, and <main> with the MR base branch name, and run

eliranmal

#!/usr/bin/env bash


main() {
	log
	log_ln "hi :)"
	check_links $(cat -)
	log_ln "bye bye!"
}

eliranmal

redhat bash prompt

customize your prompt line to match your fedora

how to

• add this somewhere in your .bash_profile (or .bashrc)

eliranmal

#
# a one-liner to get raw content from github enterprise, relying on basic authentication.
# eliminates the need to create an access token and incorporate it in the url.
#
#
# fill in the blanks:
#
#   USER         your login user name for authentication (you'll be prompted for password on the terminal)
#   GHE_DOMAIN   the github enterprise custom domain

eliranmal

(function (triggerIntervalSeconds) {

	triggerIntervalSeconds = triggerIntervalSeconds || (60 * 5);

	var runInterval = triggerIntervalSeconds * 1000;
	var runBuildTimeout = 300;

	function runBuild(done) {
		var runBtn = jQuery("button:contains(Run)")[0];
		console.log('opening build run dialog...');

dzzh

#!/usr/bin/env python

import os
import sys
import urllib2
import json

'''
This script queries Github for source and target branches of a pull request
and updates environment variables at TeamCity CI to make these variable

eliranmal

#!/usr/bin/env bash

# example usage:
# 
#	json_response="$(curl --flag http://whatever.man)" # -> { "status": 22, "errors": [ { "message": "oh no!" } ]  }
#	errors="$(echo "$json_response" | json_get "errors")"
#	[[ $errors ]] && {
#		msg="$(echo "$errors" | json_get "0" | json_get "message")"
#	}
json_get() {

eliranmal

#!/usr/bin/env bash


pull_request() {
	local to_branch="$1"
	if [ -z $to_branch ]; then
		to_branch="master"
	fi

  local access_token="[some access token with lots of characters]"

xjamundx

Trying Flow on my node.js code…Let’s see how this goes

Finding the getting started guide:

1. google flow
2. click “getflow.com”
3. was something else
4. google flow javascript
5. found flowtype.org
6. Click “get started” and landed here https://flowtype.org/docs/getting-started.html#_

xjamundx

This is the follow up to a post I wrote recently called From Require.js to Webpack - Party 1 (the why) which was published in my personal blog.

In that post I talked about 3 main reasons for moving from require.js to webpack:

1. Common JS support
2. NPM support
3. a healthy loader/plugin ecosystem.

Here I'll instead talk about some of the technical challenges that we faced during the migration. Despite the clear benefits in developer experience (DX) the setup was fairly difficult and I'd like to cover some of the challanges we faced to make the transition a bit easier.