Chris Deely chrisdeely

## switch-local-git-repo-to-fork.md

      
              1 file
            
          
              19 forks
            
          
              3 comments
            
          
              97 stars
            
          
                jpierson
                / switch-local-git-repo-to-fork.md
            
            
              Last active
              December 26, 2022 21:48
                — forked from jagregory/gist:710671
            
              
                How to move to a fork after cloning
              
          
    If you are like me you find yourself cloning a repo, making some proposed changes and then deciding to later contributing back using the GitHub Flow convention. Below is a set of instructions I've developed for myself on how to deal with this scenario and an explanation of why it matters based on jagregory's gist.
To follow GitHub flow you should really have created a fork initially as a public representation of the forked repository and the clone that instead. My understanding is that the typical setup would have your local repository pointing to your fork as origin and the original forked repository as upstream so that you can use these keywords in other git commands.


Clone some repo (you've probably already done this step)
git clone git@github...some-repo.git


## what-forces-layout.md

      
              1 file
            
          
              820 forks
            
          
              109 comments
            
          
              8143 stars
            
          
                paulirish
                / what-forces-layout.md
            
            
              Last active
              July 22, 2024 06:32
            
              
                What forces layout/reflow. The comprehensive list.
              
          
    What forces layout / reflow

All of the below properties or methods, when requested/called in JavaScript, will trigger the browser to synchronously calculate the style and layout*. This is also called reflow or layout thrashing, and is common performance bottleneck.
Generally, all APIs that synchronously provide layout metrics will trigger forced reflow / layout. Read on for additional cases and details.
Element APIs

Getting box metrics


elem.offsetLeft, elem.offsetTop, elem.offsetWidth, elem.offsetHeight, elem.offsetParent


## better-nodejs-require-paths.md

      
              1 file
            
          
              248 forks
            
          
              183 comments
            
          
              2365 stars
            
          
                branneman
                / better-nodejs-require-paths.md
            
            
              Last active
              June 29, 2024 16:00
            
              
                Better local require() paths for Node.js
              
          
    Better local require() paths for Node.js

Problem

When the directory structure of your Node.js application (not library!) has some depth, you end up with a lot of annoying relative paths in your require calls like:
const Article = require('../../../../app/models/article');
Those suck for maintenance and they're ugly.
Possible solutions


## deploy.ps1
#Modified and simplified version of https://www.windowsazure.com/en-us/develop/net/common-tasks/continuous-delivery/
$subscription = "[Your Subscription Name]"
$service = "[Your Azure Service Name]"
$slot = "staging" #staging or production
$package = "[ProjectName]\bin\[BuildConfigName]\app.publish\[ProjectName].cspkg"
$configuration = "[ProjectName]\bin\[BuildConfigName]\app.publish\ServiceConfiguration.Cloud.cscfg"
$timeStampFormat = "g"
$deploymentLabel = "ContinuousDeploy to $service v%build.number%"

Write-Output "Running Azure Imports"

## README.md

      
              4 files
            
          
              18 forks
            
          
              21 comments
            
          
              105 stars
            
          
                hsablonniere
                / README.md
            
            
              Created
              May 2, 2012 22:42
            
              
                scrollIntoViewIfNeeded 4 everyone!!!
              
          
    scrollIntoViewIfNeeded 4 everyone!!!

This gist provides a simple JavaScript implementation of the non-standard WebKit method scrollIntoViewIfNeeded that can be called on DOM elements.
Usage

Just use the code in index.js in your app or website. You can see usage in the test page test.html.
The parent element will only scroll if the element being called is out of the view. The boolean can force the element to be centered in the scrolling area.

  
## box-shadow.html
<!DOCTYPE html>
<html>
	<head>
		<title>Box Shadow</title>

		<style>
			.box {
				height: 150px;
				width: 300px;
				margin: 20px;
	#Modified and simplified version of https://www.windowsazure.com/en-us/develop/net/common-tasks/continuous-delivery/
	$subscription = "[Your Subscription Name]"
	$service = "[Your Azure Service Name]"
	$slot = "staging" #staging or production
	$package = "[ProjectName]\bin\[BuildConfigName]\app.publish\[ProjectName].cspkg"
	$configuration = "[ProjectName]\bin\[BuildConfigName]\app.publish\ServiceConfiguration.Cloud.cscfg"
	$timeStampFormat = "g"
	$deploymentLabel = "ContinuousDeploy to $service v%build.number%"

	Write-Output "Running Azure Imports"
	<!DOCTYPE html>
	<html>
	<head>
	<title>Box Shadow</title>

	<style>
	.box {
	height: 150px;
	width: 300px;
	margin: 20px;