frankodoom

#!/usr/bin/env bash

FILENAME=${1}
# expected to be defined in the environment
#  - AZURE_STORAGE_ACCOUNT
#  - AZURE_CONTAINER_NAME
#  - AZURE_ACCESS_KEY

# inspired by

frankodoom

using System;
using System.Collections.Generic;
using System.IO;
using System.Net.Http;

namespace PackageUploader.Azure
{
    public class AzureStorageApi
    {
        public void UploadFile(String fullFilePath, String blobSasUri, Dictionary<String, String> metadata = null)

frankodoom

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, when I started going through the process of forking and issuing pull requests, I had some trouble figuring out the proper method for doing so and made quite a few mistakes along the way. 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

frankodoom

Bootstrap 3 - Carousel/Slider Collection

Article: http://sevenx.de/blog
Demo: http://sevenx.de/demo/bootstrap-carousel

Working Examples (inline Styles, CDN Scripts)

- minimal Bootstrap Markup changes
- minimal CSS Styles
- minimal jQuery