Konstantin Büschel kbshl

## add_code_to_empty_repo.sh
# From your terminal, change to the root directory of your existing code.
# Initialize the directory under source control from the following command:
git init

# Add the existing files to the repository you have initialized:
git add .

# Commit the files:
git commit -m 'initial commit of full repository'

## access_full_source_of_commit_bitbucket_web_interface.md

      
              1 file
            
          
              0 forks
            
          
              0 comments
            
          
              0 stars
            
          
                kbshl
                / access_full_source_of_commit_bitbucket_web_interface.md
            
            
              Created
              October 10, 2016 07:01
            
              
                How to access full source of Commit in Bitbucket Web Interface From http://stackoverflow.com/questions/14528344/how-to-access-full-source-of-old-commit-in-bitbucket
              
          
    There are links to download specific tags, in the format:
https://bitbucket.org/owner/repository/get/v0.1.2.tar.gz
changing the tag name by the commit hash, like:
https://bitbucket.org/owner/repository/get/A0B1C2D.tar.gz
You can actually download a specific version.

  
## remove_falsy_object_props.js
var cleanedObj;

// Underscore >= 1.7.0
cleanedObj = _.pick(sourceObj, _.identity);

// Lodash >= 0.1.0
cleanedObj = _.pick(sourceObj, _.identity);

// Lodash >= 4.0.0
cleanedObj = _.pickBy(sourceObj);

## el_capitan_gem_install_rootless.sh
# Apparently with OSX el Capitan, there is a new security function that prevents
# you from modifying system files called Rootless.
# So you'll have 2 options:  If you install gems on "/usr/local/bin"
# there will be no problem because rootless doesn't affect this path.

sudo gem install -n /usr/local/bin GEM_NAME_HERE

## migration_file_timestamp.js
console.log(moment().format('YYYYMMDDHHmmss_'));

## alloy_module_tag.xml
<!-- Example:
<Module id="paint" module="ti.paint" method="createPaintView" eraseMode="false" strokeWidth="1.0" strokeColor="red" strokeAlpha="100" />
-->

<Module module="" method="" id="" />

## update_forked_github_repo.sh
# Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

# Fetch all the branches of that remote into remote-tracking branches,
# such as upstream/master:

git fetch upstream

# Make sure that you're on your master branch:

## update_github_fork.sh
# Add the remote, call it "upstream":

git remote add upstream https://github.com/whoever/whatever.git

# Fetch all the branches of that remote into remote-tracking branches,
# such as upstream/master:

git fetch upstream

# Make sure that you're on your master branch:

## select_node_based_on_text
# //FIRST_SELECTOR/SECOND_SELECTOR[text()='SEARCH_WORD']
# example:

/DocText/WithQuads/Page/Word[text()='July']

## get_following_sibling
# //FIRST_SELECTOR/following-sibling::SECOND_SELECTOR
# example:

//tr[td=' Color Digest '][2]/td/following-sibling::td[1]
	# From your terminal, change to the root directory of your existing code.
	# Initialize the directory under source control from the following command:
	git init

	# Add the existing files to the repository you have initialized:
	git add .

	# Commit the files:
	git commit -m 'initial commit of full repository'
	var cleanedObj;

	// Underscore >= 1.7.0
	cleanedObj = _.pick(sourceObj, _.identity);

	// Lodash >= 0.1.0
	cleanedObj = _.pick(sourceObj, _.identity);

	// Lodash >= 4.0.0
	cleanedObj = _.pickBy(sourceObj);
	# Apparently with OSX el Capitan, there is a new security function that prevents
	# you from modifying system files called Rootless.
	# So you'll have 2 options: If you install gems on "/usr/local/bin"
	# there will be no problem because rootless doesn't affect this path.

	sudo gem install -n /usr/local/bin GEM_NAME_HERE
	<!-- Example:
	<Module id="paint" module="ti.paint" method="createPaintView" eraseMode="false" strokeWidth="1.0" strokeColor="red" strokeAlpha="100" />
	-->

	<Module module="" method="" id="" />
	# Add the remote, call it "upstream":

	git remote add upstream https://github.com/whoever/whatever.git

	# Fetch all the branches of that remote into remote-tracking branches,
	# such as upstream/master:

	git fetch upstream

	# Make sure that you're on your master branch:
	# //FIRST_SELECTOR/SECOND_SELECTOR[text()='SEARCH_WORD']
	# example:

	/DocText/WithQuads/Page/Word[text()='July']
	# //FIRST_SELECTOR/following-sibling::SECOND_SELECTOR
	# example:

	//tr[td=' Color Digest '][2]/td/following-sibling::td[1]