Create new Julia packages, the easy way
Go to file
2017-08-18 02:08:03 -05:00
defaults Tweak CI files 2017-08-18 02:05:48 -05:00
docs Update documentation 2017-08-17 23:06:45 -05:00
licenses Copy over files 2017-08-11 17:18:09 -05:00
src Add requirements keyword to Template 2017-08-18 02:08:03 -05:00
test Add requirements keyword to Template 2017-08-18 02:08:03 -05:00
.appveyor.yml Tweak CI files 2017-08-18 02:05:48 -05:00
.codecov.yml PkgTemplates generated files 2017-08-10 12:13:01 -05:00
.gitignore Rework code, fix/add tests, fix/add docs. All the things. 2017-08-17 17:06:05 -05:00
.travis.yml Tweak CI files 2017-08-18 02:05:48 -05:00
LICENSE Remove license file extension 2017-08-16 01:15:16 -05:00
README.md Rework code, fix/add tests, fix/add docs. All the things. 2017-08-17 17:06:05 -05:00
REQUIRE Use AutoHashEquals 2017-08-14 13:12:37 -05:00

PkgTemplates

Stable Latest Build Status Build Status CodeCov

PkgTemplates is a Julia package for creating new Julia packages in an easy, repeatable, and customizable way.

Installation

PkgTemplates is registered in METADATA.jl, so run Pkg.add("PkgTemplates") for the latest release, or Pkg.clone("PkgTemplates") for the development version.

Usage

The simplest template only requires your GitHub username.

julia> using PkgTemplates

julia> t = Template(; user="invenia")

julia> generate("MyPkg", t)
INFO: Initialized git repo at /tmp/tmpvaHVki/MyPkg
INFO: Made initial empty commit
INFO: Set remote origin to https://github.com/invenia/MyPkg.jl
INFO: Staged 5 files/directories: src/, test/, REQUIRE, .gitignore, README.md
INFO: Committed files generated by PkgTemplates
INFO: Copying temporary package directory into /home/degraafc/.julia/v0.6/
INFO: Finished

julia> run(`ls -R $(Pkg.dir("MyPkg"))`)
/home/degraafc/.julia/v0.6/MyPkg:
README.md  REQUIRE  src  test

/home/degraafc/.julia/v0.6/MyPkg/src:
MyPkg.jl

/home/degraafc/.julia/v0.6/MyPkg/test:
runtests.jl

However, we can also configure a number of keyword arguments to Template and generate:

julia> t = Template(;
           user="invenia",
           license="MIT",
           authors=["Chris de Graaf", "Invenia Technical Computing Corporation"],
           years="2016-2017",
           dir=joinpath(ENV["HOME"], "code"),
           julia_version=v"0.5.2",
           git_config=Dict("diff.renames" => true),
           plugins=[
               TravisCI(),
               CodeCov(; config_file=nothing),
               AppVeyor(),
               GitHubPages(; assets=[joinpath(ENV["HOME"], "invenia.css")]),
           ],
       )

julia> generate("MyPkg", t; force=true, ssh=true)
INFO: Initialized git repo at /tmp/tmpe0dWY5/MyPkg
INFO: Applying git configuration
INFO: Made initial empty commit
INFO: Set remote origin to git@github.com:invenia/MyPkg.jl.git
INFO: Created empty gh-pages branch
INFO: Staged 9 files/directories: src/, test/, REQUIRE, README.md, .gitignore, LICENSE, .travis.yml, .appveyor.yml, docs/
INFO: Committed files generated by PkgTemplates
INFO: Copying temporary package directory into /home/degraafc/code/
INFO: Finished
WARNING: Remember to push all created branches to your remote: git push --all

Information on each keyword as well as plugin types can be found in the documentation.

Comparison to PkgDev

PkgTemplates is similar in functionality to PkgDev's generate function. However, PkgTemplates offers more customizability in templates and more extensibility via plugins. For the package registration and release management features that PkgTemplates doesn't include, you are encouraged to use AttoBot instead.

Contributing

It's extremely easy to extend PkgTemplates with new plugins. To get started, check out the plugin development guide.