Update files according to Contributors library guidelines.

Author: th-awake

.github/ISSUE_TEMPLATE/bug-report.md

@@ -7,7 +7,7 @@ assignees: ""
 ---
 
 **Describe the bug**
-A clear and concise description of what the bug is.
+A clear and concise description of the bug.
 
 **To Reproduce**
 A minimal code example (preferably a runnable example on [Try PureScript](https://try.purescript.org)!) or steps to reproduce the issue.

.github/ISSUE_TEMPLATE/change-request.md

@@ -2,12 +2,12 @@
 name: Change request
 about: Propose an improvement to this library
 title: ""
-labels: enhancement
+labels: ""
 assignees: ""
 ---
 
 **Is your change request related to a problem? Please describe.**
-A clear and concise description of what the problem is.
+A clear and concise description of the problem.
 
 Examples:
 

.github/contributing.md

@@ -1,37 +1,5 @@
-# Contributing
+# Contributing to Argonaut Codecs
 
-Thanks for your interest in contributing to argonaut-codecs! This file is a short, sweet introduction to contributing to this project. We ask that all new contributors read it before their first contribution to make sure we can get your work merged.
+Thanks for your interest in contributing to `argonaut-codecs`! We welcome new contributions regardless of your level of experience or familiarity with PureScript.
 
-## Getting Started
-
-### Do I belong here?
-
-Everyone is welcome! People of all experience levels can join, begin contributing, and feel comfortable and safe making mistakes. People of all backgrounds belong here so long as they treat others with dignity and respect and do not harass, belittle, or insult others.
-
-### What is the correct way to ask a question?
-
-Feel free to ask questions by [opening an issue](https://github.com/purescript-contrib/purescript-argonaut-codecs/issues)! You can also ask questions on the [PureScript Discourse](https://discourse.purescript.org), or on the [Functional Programming Slack](https://functionalprogramming.slack.com) ([join](https://fpchat-invite.herokuapp.com)!) in the `#purescript` and `#purescript-beginners` channels.
-
-### I'd like to help, how do I pick something to work on?
-
-Any [open issue](https://github.com/purescript-contrib/purescript-argonaut-codecs/issues) that is not assigned to anyone is good to work on! If it's your first time contributing it's probably best to pick an issue marked [good first issue](https://github.com/purescript-contrib/purescript-argonaut-codecs/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue). You can also search for issues marked [help-wanted](https://github.com/purescript-contrib/purescript-argonaut-codecs/issues?q=is%3Aissue+is%3Aopen+label%3A%22help+wanted).
-
-The easiest way you can help is by contributing documentation (issues marked [document me](https://github.com/purescript-contrib/purescript-argonaut-codecs/issues?q=is%3Aissue+is%3Aopen+label%3A%22document+me). If you'd like to contribute documentation, we suggest [reading about the four kinds of documentation](https://documentation.divio.com).
-
-Your contribution can be as small as copy-pasting some instructions from an issue into the documentation! Everything is welcome.
-
-## Developing argonaut-codecs
-
-All `purescript-contrib` libraries use recent versions of [PureScript](https://github.com/purescript/purescript), [Spago](https://github.com/purescript/spago), and [psa](https://github.com/natefaubion/purescript-psa). Any additional development dependencies can be installed via NPM and are listed in the `package.json` file for the repository.
-
-### Proposing changes
-
-If you would like to contribute code, tests, or documentation, please feel free to open a pull request for small changes. For large changes we recommend you first open an issue to propose your change and ensure that the maintainers are on board before you spend time implementing the change. We want to respect your time and effort. We can also assign the issue to you if you would like to make sure you're the one to work on it.
-
-### Merging changes
-
-All changes must happen through a pull request. Everyone with commit access can merge changes, though by convention we like to wait for two approvals for non-trivial changes. All pull requests must pass continuous integration; if the change adds new code we may also ask that you add a test.
-
-## How do I get the "commit bit"?
-
-If you'd like to take part in maintaining argonaut-codecs, just ask! We hand out the commit bit to folks who display sustained interest in the project. You can ask directly (for example: on Slack or via a DM on Discourse) or by opening an issue -- whichever you prefer!
+Every library in the Contributors organization shares a simple handbook that helps new contributors get started. With that in mind, please [read the short contributing guide on purescript-contrib/governance](https://github.com/purescript-contrib/governance/blob/main/contributing.md) before contributing to this library.

.github/pull_request_template.md

@@ -1,15 +1,11 @@
-## What does this pull request do?
+**Description of the change**
+Clearly and concisely describe the purpose of the pull request. If this PR relates to an existing issue or change proposal, please link to it. Include any other background context that would help reviewers understand the motivation for this PR.
 
-Please describe the purpose of the pull request, including any background context and links to related issues. If this introduces a large change to the project, please describe what you have implemented.
+---
 
-## Where should the reviewer start?
+**Checklist:**
 
-Help save the reviewer time by highlighting the most important sections of code.
-
-## How should this be manually tested?
-
-If this is a new feature, you should provide new test coverage. If it fixes an existing bug, you should provide a failing test case this change fixes. Other than automated testing, what manual tests can the reviewer perform to verify your work?
-
-## Other Notes:
-
-Does the project documentation need to be updated? Should we introduce a new example, or update any existing examples? Does this PR require any other follow-up tasks?
+- [ ] Added the change to the changelog's "Unreleased" section with a link to this PR and your username
+- [ ] Linked any existing issues or proposals that this pull request should close
+- [ ] Updated or added relevant documentation in the README and/or documentation directory
+- [ ] Added a test for the contribution (if applicable)

.github/workflows/ci.yml

@@ -2,17 +2,19 @@ name: CI
 
 on:
   push:
-    branches: [master]
+    branches: [main]
   pull_request:
-    branches: [master]
+    branches: [main]
 
 jobs:
   build:
     runs-on: ubuntu-latest
 
     steps:
       - uses: actions/checkout@v2
-      - uses: thomashoneyman/setup-purescript@main
+
+      - name: Set up a PureScript toolchain
+        uses: purescript-contrib/setup-purescript@main
 
       - name: Cache PureScript dependencies
         uses: actions/cache@v2
@@ -22,8 +24,11 @@ jobs:
             .spago
             output
 
+      - name: Install dependencies
+        run: spago install
+
       - name: Build source
-        run: spago build
+        run: spago build --no-install --purs-args '--censor-lib --strict'
 
       - name: Run tests
         run: spago test --no-install

.github/workflows/stale.yml

@@ -0,0 +1,23 @@
+name: "Stale"
+
+on:
+  schedule:
+    - cron: "0 0 * * *"
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v3
+        env:
+          days-until-stale: 60
+          days-until-close: 14
+        with:
+          repo-token: ${{ secrets.GITHUB_TOKEN }}
+          stale-issue-message: "This issue is stale because it has been open for ${{ env.days-until-stale }} days with no activity. Remove the stale label or comment to keep this issue open. Otherwise, this issue will be closed in ${{ env.days-until-close }} days."
+          stale-pr-message: "This pull request is stale because it has been open for ${{ env.days-until-stale }} days with no activity. Remove the stale label or comment to keep this pull request open. Otherwise, this pull request will be closed in ${{ env.days-until-close }} days."
+          days-before-stale: ${{ env.days-until-stale }}
+          days-before-close: ${{ env.days-until-close }}
+          stale-issue-label: "stale"
+          stale-pr-label: "stale"
+          exempt-pr-labels: "breaking change"

.gitignore

@@ -1,16 +1,7 @@
 .*
 !.gitignore
 !.github
-!.eslintrc.json
 !.editorconfig
 
-# Dependencies
-bower_components
-node_modules
-
-# Generated files
 output
 generated-docs
-
-# Non-NPM lockfiles
-*.lock

README.md

@@ -1,9 +1,8 @@
 # Argonaut Codecs
 
-[![CI](https://github.com/purescript-contrib/purescript-argonaut-codecs/workflows/CI/badge.svg?branch=master)](https://github.com/purescript-contrib/purescript-argonaut-codecs/actions?query=workflow%3ACI+branch%3Amaster)
+[![CI](https://github.com/purescript-contrib/purescript-argonaut-codecs/workflows/CI/badge.svg?branch=main)](https://github.com/purescript-contrib/purescript-argonaut-codecs/actions?query=workflow%3ACI+branch%3Amain)
 [![Release](http://img.shields.io/github/release/purescript-contrib/purescript-argonaut-codecs.svg)](https://github.com/purescript-contrib/purescript-argonaut-codecs/releases)
 [![Pursuit](http://pursuit.purescript.org/packages/purescript-argonaut-codecs/badge)](http://pursuit.purescript.org/packages/purescript-argonaut-codecs)
-[![Maintainer: garyb](https://img.shields.io/badge/maintainer-garyb-teal.svg)](http://github.com/garyb)
 [![Maintainer: thomashoneyman](https://img.shields.io/badge/maintainer-thomashoneyman-teal.svg)](http://github.com/thomashoneyman)
 
 [Argonaut](https://github.com/purescript-contrib/purescript-argonaut) is a collection of libraries for working with JSON in PureScript. `argonaut-codecs` provides codecs based on the `EncodeJson` and `DecodeJson` type classes, along with instances for common data types and combinators for encoding and decoding `Json` values.
@@ -19,13 +18,13 @@ The quick start will get you up and running with the basics of `argonaut-codecs`
 
 ## Installation
 
-Install with [Spago](https://github.com/purescript/spago):
+Install `argonaut-codecs` with [Spago](https://github.com/purescript/spago):
 
 ```sh
 spago install argonaut-codecs
 ```
 
-or install as part of the [Argonaut](https://github.com/purescript-contrib/purescript-argonaut) bundle:
+or install it as part of the [Argonaut](https://github.com/purescript-contrib/purescript-argonaut) bundle:
 
 ```sh
 spago install argonaut
@@ -71,11 +70,11 @@ Left "An error occurred while decoding a JSON value:\n  At object key 'age':\n
 
 ## Documentation
 
-You can find `argonaut-codecs` documentation in a few places:
+`argonaut-codecs` documentation is stored in a few places:
 
 1. Module documentation is [published on Pursuit](https://pursuit.purescript.org/packages/purescript-argonaut-codecs).
-2. The tutorial and other written documentation is kept in [the docs directory](./docs).
-3. Additional usage examples can be found in [the PureScript Cookbook](https://github.com/JordanMartinez/purescript-cookbook)
+2. Written documentation and [the changelog](./docs/CHANGELOG.md) are kept in [the docs directory](./docs).
+3. Usage examples can be found in [the test suite](./test).
 
 If you get stuck, there are several ways to get help:
 
@@ -86,7 +85,7 @@ If you get stuck, there are several ways to get help:
 
 You can contribute to `argonaut-codecs` in several ways:
 
-1. If you encounter a problem or have a question, please [open an issue](https://github.com/purescript-contrib/purescript-argonaut-codecs/issues) issue. We'll do our best to work with you to resolve or answer it.
+1. If you encounter a problem or have a question, please [open an issue](https://github.com/purescript-contrib/purescript-argonaut-codecs/issues). We'll do our best to work with you to resolve or answer it.
 
 2. If you would like to contribute code, tests, or documentation, please [read the contributor guide](./.github/CONTRIBUTING.md). It's a short, helpful introduction to contributing to this library, including development instructions.
 

docs/CHANGELOG.md

@@ -0,0 +1,15 @@
+# Changelog
+
+Notable changes to this project are documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/) and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+Breaking changes (😱!!!):
+
+New features:
+
+Bugfixes:
+
+Other improvements:
+
+## [0.0.0] - 2020-01-01