jwu910

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

jwu910

array,list,linked list,object oriented,variable,source control,git,github,javascript,python,dictionary,declare,vue,template,pricing engine,exchange,operators,camel case,encompass,for loop,figma,mockup,wireframe,java,pycharm,vscode,machine learning,artificial intelligence,shell,docker,amazon web services,while loop,SQL Injection,cross-site scripting,cross-site request forgery,distributed denial of service,testing,automation,API,routes,Analytics,workflow management,changeset,loan pipeline,slack,email,okta,heroku,sentry,on call,drag-or-drop,standup,retro,sprint planning,grooming,jira,bug,story,story points,circle ci,continuous integration,code review,pull request,pascal case,kebab case

jwu910

sudo mkdir -p /var/run/mysqld; sudo chown mysql /var/run/mysqld
sudo mysqld_safe --skip-grant-tables &

Or

mkdir -p /var/run/mysqld && chown mysql:mysql /var/run/mysqld  

jwu910

# Get project root path
function rootLevel {
  git rev-parse --show-toplevel 2>/dev/null
}

# Liferay run-gradle script to find gradle files in parent directories for portlet deployment
function rungradle {
  local current_dir=$(pwd)
  # Rename settings.gradle temporarily
  if [ -e settings.gradle ]; then

jwu910

#!/bin/bash

NSCRIPT_SCRIPT_DIR="${NSCRIPT_SCRIPT_DIR:?Please set the "NSCRIPT_SCRIPT_DIR" environment variable. nscript will use it for storing shell scripts}"

if [[ ! -d "${NSCRIPT_SCRIPT_DIR}" ]]
then
	echo "The NSCRIPT_SCRIPT_DIR value \"${NSCRIPT_SCRIPT_DIR}\" is not a valid directory."

	exit 1
fi

jwu910

# Takes one optional argument [JIRA TICKET NUM] in the format XXXX-0000. e.g. LOOP-1234.
# Opens all files changed associated with JIRA ticket. If no argument is provided, JIRA ticket is attempted to be taken from branch name.
function openCommitsIn {
  local FILE_EDITOR="subl"
  local MIN_THRESH=5

  filesChanged() {
    git log --grep "$1" --stat --name-only | grep -E ".(tag|jsp.?|vm|ftl|js|(s)?css)$" | sort | uniq
  }