# Workflow for Julia scripts

**URL:** <https://discourse.julialang.org/t/workflow-for-julia-scripts/6453>\
**Category:** New to Julia\
**Created:** [October 15, 2017, 8:41pm UTC](https://discourse.julialang.org/t/workflow-for-julia-scripts/6453 "2017-10-15T20:41:16Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![djsegal](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/djsegal/32/13752_2.png) [@djsegal](https://discourse.julialang.org/u/djsegal)\
**Post date:** [October 16, 2017, 6:19pm UTC](https://discourse.julialang.org/t/workflow-for-julia-scripts/6453/13 "2017-10-16T18:19:06Z")

</div>

The master branch of [Julz](https://github.com/djsegal/julz) does what you want to do.

- `Julz.new(<pkg_name>, "mit")` makes a package
- `Julz.generate("task", <task_name>)` makes a task (if you’re in the right directory)
- `using <pkg_name>` loads the package with every files inside it (done automagically w/ `Revise` added)
- `Julz.run(<task_name>)` will then run the desired task

All this can be done from the command line also, without the need to explicitly open the REPL

* * *

this was born from similar posts:

- [Distinguishing projects from packages - #40 by tamasgal](https://discourse.julialang.org/t/distinguishing-projects-from-packages/153/40)
- [Standard ways to run common commands - #12 by djsegal](https://discourse.julialang.org/t/standard-ways-to-run-common-commands/154/12)

* * *

official juleps issue related to runnable packages (as mentioned by @ChrisRackauckas)

- [https://github.com/JuliaLang/Juleps/issues/20](https://github.com/JuliaLang/Juleps/issues/20)

---

_[View the full topic](https://discourse.julialang.org/t/workflow-for-julia-scripts/6453)._