Format files on commit

Author: rick-nu

.gitignore

@@ -0,0 +1 @@
+node_modules/

.husky/pre-commit

@@ -0,0 +1,4 @@
+#!/usr/bin/env sh
+. "$(dirname -- "$0")/_/husky.sh"
+
+npm run format

.prettierrc.json

@@ -0,0 +1,8 @@
+{
+	"trailingComma": "es5",
+	"semi": true,
+	"singleQuote": true,
+	"useTabs": true,
+	"printWidth": 100,
+	"proseWrap": "always"
+}

README.md

@@ -1,42 +1,45 @@
 # Taskfile
 
-A `./Taskfile` is a task runner in plain and easy [Bash](https://nl.wikipedia.org/wiki/Bash). It adds a list of available tasks to your project.
+A `./Taskfile` is a task runner in plain and easy [Bash](https://nl.wikipedia.org/wiki/Bash). It
+adds a list of available tasks to your project.
 
 ![CLI Taskfile preview](./images/cli-preview.gif)
 
 ## Why
 
-- Works on any OS (any bash terminal)
-- A uniform way to run your projects
-- Very easy to use
-- Automate your most common tasks (updating, starting, building, etc...)
-- Easy to understand and maintain
+-   Works on any OS (any bash terminal)
+-   A uniform way to run your projects
+-   Very easy to use
+-   Automate your most common tasks (updating, starting, building, etc...)
+-   Easy to understand and maintain
 
 # Create your own taskfile
 
-This project gives you a `Taskfile` base, and gives you a collection of usefull tasks to help out on your project.
+This project gives you a `Taskfile` base, and gives you a collection of usefull tasks to help out on
+your project.
 
-- [The Taskfile base](./taskfile-base.md)
+-   [The Taskfile base](./taskfile-base.md)
 
-We strongly recommend that your project uses a project section containing a `init` and a `update` task. Check out our
-example:
+We strongly recommend that your project uses a project section containing a `init` and a `update`
+task. Check out our example:
 
-- [Project section](./section/project.md)
+-   [Project section](./section/project.md)
 
 ## Usefull tasks
 
 Check out the following sections for tasks that could be helpfull for your project's Taskfile:
 
-- [Docker](./section/docker.md)
-- [GitHub](./section/github.md)
-- [GitLab](./section/gitlab.md)
+-   [Docker](./section/docker.md)
+-   [GitHub](./section/github.md)
+-   [GitLab](./section/gitlab.md)
 
 # Credits
 
-This Taskfile setup is based on [Adrian Cooney's Taskfile setup](https://github.com/adriancooney/Taskfile) and
+This Taskfile setup is based on
+[Adrian Cooney's Taskfile setup](https://github.com/adriancooney/Taskfile) and
 [Enrise](https://enrise.com) their internal implementation of the Taskfile.
 
 # Contribute
 
-Feel free to add your own Taskfile tasks via a PR. The more usefull tasks, the easier we make the life of other
-developers.
+Feel free to add your own Taskfile tasks via a PR. The more usefull tasks, the easier we make the
+life of other developers.

package-lock.json

@@ -0,0 +1,40 @@
+{
+	"name": "@futureportal/taskfile",
+	"version": "1.0.0",
+	"description": "A ./Taskfile is a task runner in plain and easy Bash. It adds a list of available tasks to your project.",
+	"scripts": {
+		"format": "prettier --write .",
+		"prepare": "husky install"
+	},
+	"repository": {
+		"type": "git",
+		"url": "git+https://github.com/FuturePortal/Taskfile.git"
+	},
+	"keywords": [
+		"bash",
+		"cli",
+		"automation",
+		"makefile",
+		"task-runner",
+		"taskfile"
+	],
+	"authors": [
+		{
+			"name": "Rick van der Staaij",
+			"url": "https://rick.nu"
+		},
+		{
+			"name": "Contributors",
+			"url": "https://github.com/FuturePortal/Taskfile/graphs/contributors"
+		}
+	],
+	"license": "MIT",
+	"bugs": {
+		"url": "https://github.com/FuturePortal/Taskfile/issues"
+	},
+	"homepage": "https://github.com/FuturePortal/Taskfile#readme",
+	"devDependencies": {
+		"husky": "^8.0.1",
+		"prettier": "^2.7.1"
+	}
+}

package.json

@@ -1,7 +1,7 @@
 # GitHub
 
-If you use GitHub and want an easy way to check out Pull Requests locally,
-`task:pr` is a great addition to your project section in the Taskfile.
+If you use GitHub and want an easy way to check out Pull Requests locally, `task:pr` is a great
+addition to your project section in the Taskfile.
 
 ```bash
 # ===========================

section/github.md

@@ -1,7 +1,7 @@
 # GitLab
 
-If you use GitLab and want an easy way to check out Merge Requests locally,
-`task:mr` is a great addition to your project section in the Taskfile.
+If you use GitLab and want an easy way to check out Merge Requests locally, `task:mr` is a great
+addition to your project section in the Taskfile.
 
 ```bash
 # ===========================

section/gitlab.md

@@ -1,9 +1,8 @@
 # Project section
 
-A project section can be very usefull to quickly get your project up and running,
-including the latest changes. A common practice is to include a `task:init` to get your
-entire project up and running with a single command, and a `task:update` to make sure everything
-is up to date.
+A project section can be very usefull to quickly get your project up and running, including the
+latest changes. A common practice is to include a `task:init` to get your entire project up and
+running with a single command, and a `task:update` to make sure everything is up to date.
 
 ```bash
 # ===========================

section/project.md

@@ -1,6 +1,7 @@
 # The Taskfile base
 
-Below is the Taskfile base we recommend you use. Below we will explain what sections are in the base and why.
+Below is the Taskfile base we recommend you use. Below we will explain what sections are in the base
+and why.
 
 ```bash
 #!/bin/bash
@@ -67,14 +68,15 @@ banner
 
 ## Banner
 
-By default we include a banner in your Taskfile. In the base you have a pretty ascii art of "Taskfile", but we recommend
-you replace this with your own project title. You can use http://patorjk.com/software/taag/ for that.
+By default we include a banner in your Taskfile. In the base you have a pretty ascii art of
+"Taskfile", but we recommend you replace this with your own project title. You can use
+http://patorjk.com/software/taag/ for that.
 
 ## Title
 
-In order to give all the tasks a pretty and clear structre, a title function is added that we recommend you use at
-the start of every task. This will create a nice divider and let your user know that your Taskfile is about to start
-a new process.
+In order to give all the tasks a pretty and clear structre, a title function is added that we
+recommend you use at the start of every task. This will create a nice divider and let your user know
+that your Taskfile is about to start a new process.
 
 ```bash
 function task:my-new-task { ## My new task example
@@ -85,24 +87,27 @@ function task:my-new-task { ## My new task example
 
 ## Help section
 
-A help section for your Taskfile is generated automatically. This is done by scanning the Taskfile itself, and checking
-if a line contains `##` (double comment). When it finds a `##`, it will either use the line as a new section in the
-help overview, or when it's combined with a `function task:* { ## Descriptoin` then the comment will be used as the
-task description. Using this will give your user a clear overview of what tasks can be run.
+A help section for your Taskfile is generated automatically. This is done by scanning the Taskfile
+itself, and checking if a line contains `##` (double comment). When it finds a `##`, it will either
+use the line as a new section in the help overview, or when it's combined with a
+`function task:* { ## Descriptoin` then the comment will be used as the task description. Using this
+will give your user a clear overview of what tasks can be run.
 
 ## PATH
 
 In the taskfile base, you see that the PATH variable is updated with an additional path
-(`PATH=./node_modules/.bin:$PATH`). In this example `./node_modules/.bin` is added to the bash PATH variable. For
-example, if you have a `eslint` binary in that folder, you can now call `eslint --fix .` directly from your tasks,
-instead of having to call `./node_modules/.bin/eslint --fix .`. If you don't need it, remove it. If you need to include
-a different binary path, update it.
+(`PATH=./node_modules/.bin:$PATH`). In this example `./node_modules/.bin` is added to the bash PATH
+variable. For example, if you have a `eslint` binary in that folder, you can now call
+`eslint --fix .` directly from your tasks, instead of having to call
+`./node_modules/.bin/eslint --fix .`. If you don't need it, remove it. If you need to include a
+different binary path, update it.
 
 ## Shorthand
 
-If you're a lazy developer (that's a good thing, trust me), you're probably already tired of having to type
-`./Taskfile <task>` all the time. The `task:shorthand` gives you a quick and easy option to create a `task` binary on
-your system, so you can use `task <task>` in the future. It will look for a `Taskfile` in the current directory.
+If you're a lazy developer (that's a good thing, trust me), you're probably already tired of having
+to type `./Taskfile <task>` all the time. The `task:shorthand` gives you a quick and easy option to
+create a `task` binary on your system, so you can use `task <task>` in the future. It will look for
+a `Taskfile` in the current directory.
 
 # Adding relevant tasks