Developer Guide
If you are planning significant changes, open an issue first. The ColPrac guidelines are recommended.
One-Time Local Setup
This procedure is required only once.
- Clone the repository.
git clone https://github.com/ohno/MyPkg53.jl.git cd MyPkg53.jl - Install development tools, Revise.jl and Runic.jl.
julia --startup-file=no -e 'import Pkg; Pkg.add("Revise")' julia --project=@runic --startup-file=no -e 'using Pkg; Pkg.add("Runic")'
Daily Development Flow
This is the typical workflow with commands.
- Start an interactive session with Revise.jl.
cd MyPkg53.jl julia --startup-file=no -i -E 'using Revise; import Pkg; Pkg.activate("."); using MyPkg53' - Change the source code. To change the source code:
- When making new functions or updating docstrings, refer to Documenter: Adding docstrings.
- If you need a new dependency, use
julia --project=. --startup-file=no -e 'import Pkg; Pkg.add("SomePackage"); Pkg.resolve(); Pkg.instantiate()'. ReplaceSomePackagewith the actual package name.
- Format the source code with Runic.jl.
julia --project=@runic --startup-file=no -e 'using Runic; exit(Runic.main(ARGS))' -- --inplace . - Run the tests.
julia --project=. --startup-file=no -e 'using Pkg; Pkg.test()' - Build the documentation locally.
julia --project=docs --startup-file=no -e 'using Pkg; Pkg.develop(PackageSpec(path=pwd())); Pkg.instantiate();' julia --project=docs --startup-file=no -e 'include("docs/make.jl")' - Submit a pull request (after steps 3–5 succeed).
For Julia package development basics, see:
Versioning and Registering (for Maintainers)
This project follows Semantic Versioning. When bumping the version, update the version number in:
To register this package in the General registry, install Registrator and use via the GitHub App.