indidatajones

# Compiled source #
###################
*.com
*.class
*.dll
*.exe
*.o
*.so

# Packages #

indidatajones

Create a new gist on github

codehub://x-callback-url/gist/create

? description

A string description of the Gist. Default is empty & public

indidatajones

Porting a Google Chrome extension

source

The browser extension APIs are designed to promote cross-browser compatibility among extensions. The WebExtension APIs is therefore, to a large extent, code-compatible with the extension API supported by Google Chrome and Opera. Extensions written for these browsers will, in most cases, run in Firefox with just a few changes. Almost all of the WebExtension APIs provide support for callback functions under the chrome namespace, the same as Chrome. The only APIs that aren't supported in the chrome namespace are those that are intentionally incompatible with Chrome. In those cases, the API documentation page states that support is provided only in the browser namespace. The process of porting an extension from Chrome or Opera is, therefore, relatively straightforward:

Review your use of manifest.json features and Chrome extension APIs against the Chrome incompatibilities reference. Mozilla provides a service that can help to automate this

indidatajones

##Simply annoying Tweets

Annoyingly extended words (4+ of the same letter in a phrase): OOOOHHHHMMMMYYYYGGGGOOOODDDD

([a-z])/1{4}

Tweet w/ just a single hashtag: #omgthissucks

^ *#[^ ]+$

indidatajones

The README Checklist

A helpful checklist to gauge how your README is coming along:

• One-liner explaining the purpose of the module
• Necessary background context & links
• Potentially unfamiliar terms link to informative sources
• Clear, runnable example of usage
• Installation instructions
• Extensive API documentation
• Performs cognitive funneling

indidatajones

A guide to understanding the importance of commit messages and how to write them well.

It may help you to learn what a commit is, why it is important to write good messages, best practices and some tips to plan and (re)write a good commit history.

What is a "commit"?

In simple terms, a commit is a snapshot of your local files, written in your local repository. Contrary to what some people think, git doesn't store only the difference between the files, it stores a full version of all files. For files that didn't change from one commit to another, git stores just a link to the previous identical file that is already stored.

indidatajones

Contributor Guidelines

You can create guidelines to communicate how people should contribute to your project.

ATOM

Contributing to Atom

👍🎉 First off, thanks for taking the time to contribute! 🎉👍

indidatajones

Attribution 4.0 International

=======================================================================

Creative Commons Corporation ("Creative Commons") is not a law firm and does not provide legal services or legal advice. Distribution of Creative Commons public licenses does not create a lawyer-client or other relationship. Creative Commons makes its licenses and related information available on an "as-is" basis. Creative Commons gives no warranties regarding its licenses, any material licensed under their

indidatajones

Contributor Covenant Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body

indidatajones

The README: Your one-stop shop

A README is a module consumer's first -- and maybe only -- look into your creation. The consumer wants a module to fulfill their need, so you must explain exactly what need your module fills, and how effectively it does so.

Your job is to

1. tell them what it is (with context)
2. show them what it looks like in action