Hoo Ja Oh hoojaoh

Local SSL websites on macOS Sierra

These instructions will guide you through the process of setting up local, trusted websites on your own computer.

These instructions are intended to be used on macOS Sierra, but they have been known to work in El Capitan, Yosemite, Mavericks, and Mountain Lion.

NOTE: You may substitute the edit command for nano, vim, or whatever the editor of your choice is. Personally, I forward the edit command to Sublime Text:

alias edit="/Applications/Sublime\ Text.app/Contents/SharedSupport/bin/subl"

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

I'm doing some research on how companies use GitHub Enterprise (or public GitHub) internally. If you can help out by answering a few questions, I'd greatly appreciate it.

What is the primary setup? Is there an organization and each official repo is owned by that organization?
Does every engineer have a fork of each repo they're working on?
Are engineers allowed to push directly to the official repo? Or must all commits go through a pull request?
Do engineers work on feature branches on the main repo or on their own forks?
Do you require engineers to squash commits and rebase before merging?
Overall, what is the workflow for getting a new commit into the main repository?
What sort of hooks do you make use of?
Are there any ops issues you encountered? (Scaling, unforeseen downtime, etc.)

	#include <stdio.h>
	#include <cs50.h>
	#include <string.h>
	#include <ctype.h>

	/**
	*
	* Write, in a file called initials.c, a program that prompts a user for
	* their name (using GetString to obtain their name as a string) and then
	* outputs their initials in uppercase with no spaces or periods,

	Moved to a proprer repositoy, TSWS is a real boy now!

	https://github.com/dfletcher/tsws

	PRs welcomed.

	(function () {
	alert('done');
	}())