view release on metacpan or  search on metacpan

COPYING  view on Meta::CPAN

  The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities.  However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work.  For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.

  The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.

  The Corresponding Source for a work in source code form is that
same work.

  2. Basic Permissions.

Changes  view on Meta::CPAN

    - API::GitForge::Role::GitForge::clean_repo(): try to unprotect
      fork branches before deleting them, if GitForge API library
      supports doing this.
    - API::GitForge::Role::GitForge::clean_repo(): push the gitforge
      branch using Git::Wrapper again.
      During early testing, this seemed to hang after pushing to
      GitLab installations, but it seems to work well now.

0.002     2020-03-09 12:17:47-07:00 America/Phoenix
    - Implement API::GitForge::GitLab::_ensure_repo().
    - Add git repo metadata to dist.ini.
    - Don't disable merge requests in GitLab clean forks.
      Otherwise we can't submit merge requests upstream.
    - Code cleanup.

0.001     2020-02-16 16:20:35-07:00 America/Phoenix
    - First public release.