view release on metacpan or  search on metacpan

HOWTO  view on Meta::CPAN

Next, create a '.gitc' file inside of the root of your git project.  In that
file, enter:

name: This is the name of my project.

You can imagine what you should put there.

Add and commit this file.

Next, you'll need to make sure that the requisite branches are available on the
remote server.  Create a test, stage, and prod branch to coincide with the
config file.

After that, you're done.

Some common gitc commands:

    open <ticket #> - Opens a new changeset in a new branch -- this gives you a
    clean checkout of the code to start hacking on.  If you have an ITS (Issue
    Tracking System) set up, it will update its status and put a note on it
    saying you've done this.

    edit <ticket #> - This lets you edit a previously existing ticket.  Usually
    to fix a failure from a code review.

    submit <reviewer> - This submits the current changeset's changes to a reviewer.

    fail - This is if you're the reviewer of an application and have decided
    something in the code/changeset makes it unpassable.

    pass - Merges the code to your master branch, and marks it ready for promotion.

    promote <target> - Used to promote code into <target> branch.  It will
    merge it, and then give you a chance to go play with it and make sure it
    works out OK.

LICENSE  view on Meta::CPAN

  Each version is given a distinguishing version number.  If the
Program specifies that a certain numbered version of the GNU Affero General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation.  If the Program does not specify a version number of the
GNU Affero General Public License, you may choose any version ever published
by the Free Software Foundation.

  If the Program specifies that a proxy can decide which future
versions of the GNU Affero General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.

  Later license versions may give you additional or different
permissions.  However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.

  15. Disclaimer of Warranty.

bin/gitc-submit  view on Meta::CPAN

    return;
};

# reinstate any changes present when we started
git "stash apply $stash" if $stash;
exec "gitc pass --from-self-review" if $self_review;
exit;

################################ helper subs ########################

# decide who should review this changeset
sub find_reviewer {
    my $reviewer = shift or die "You must specify a reviewer\n";

    # handle self-review for dataload projects
    my $current_user = get_user_name();
    if ( $reviewer eq $current_user ) {
        if ( project_config()->{'self submit'} ) {
            $self_review = 1;
            $skip_email  = 1;
            $keep        = 1;