aggieben

Any top-level comment on pull request ought be tagged with one of four emojis:

• ❓ for a non-blocking comment that asks for clarification. The pull request author must answer the question before the pull request is merged, but does not have to wait for the comment author to re-review before merging.

• 🎨 for a non-blocking comment that proposes a refactor or cleanup. The pull request author does not have to address the comment for the pull request to merge.

• ⚠️ for a blocking comment that must be addressed before the pull request can merge. The comment's author should leave a Request Changes review, and is responsible for re-reviewing once the pull request author has addressed the issue.

• 😻 for a comment that compliments the author for their work.

aggieben

#!/bin/bash -e
# A SHORT DESCRIPTION OF YOUR SCRIPT GOES HERE
# USAGE:
#    DESCRIPTION OF ENV VARS HERE
###############################################################################
set -e          # exit on command errors (so you MUST handle exit codes properly!)
set -o pipefail # capture fail exit codes in piped commands
#set -x         # execution tracing debug messages

# Get command info

aggieben

// ==UserScript==
// @name        CO-OP Timer Growl Reminder
// @namespace   http://coopapp.com
// @description Displays Growl notifications at a user defined interval, reminding you to track your time.
// @include     *
// @author      Andreas Schempp
// @author      Mike Green
// @version	0.1.1
// ==/UserScript==