ci: add CI.

It sucks because all of this stuff will fail, but these are the standards
we have for releasing ash packages

.github/CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, sex characteristics, gender identity and expression,
+level of experience, education, socio-economic status, nationality, personal
+appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+ advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+ address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+ professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at [email protected]. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

.github/CONTRIBUTING.md

@@ -0,0 +1,10 @@
+# Contributing to Ash
+
+* We have a zero tolerance policy for failure to abide by our code of conduct. It is very standard, but please make sure
+  you have read it.
+* Issues may be opened to propose new ideas, to ask questions, or to file bugs.
+* Before working on a feature, please talk to the core team/the rest of the community via a proposal. We are 
+  building something that needs to be cohesive and well thought out across all use cases. Our top priority is 
+  supporting real life use cases like yours, but we have to make sure that we do that in a sustainable way. The 
+  best compromise there is to make sure that discussions are centered around the *use case* for a feature, rather
+  than the propsed feature itself.

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,27 @@
+---
+name: Bug report
+about: Create a report to help us improve
+title: ''
+labels: bug, needs review
+assignees: ''
+
+-https://hexdocs.pm/ash_paper_trail--
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+A minimal set of resource definitions and calls that can reproduce the bug.
+
+**Expected behavior**
+A clear and concise description of what you expected to happen.
+
+** Runtime
+ - Elixir version
+ - Erlang version
+ - OS
+ - Ash version
+ - any related extension versions
+
+**Additional context**
+Add any other context about the problem here.

.github/ISSUE_TEMPLATE/proposal.md

@@ -0,0 +1,36 @@
+---
+name: Proposal
+about: Suggest an idea for this project
+title: ''
+labels: enhancement, needs review
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Express the feature either with a change to resource syntax, or with a change to the resource interface**
+
+For example
+
+```elixir
+  attributes do
+    attribute :foo, :integer, bar: 10 # <- Adding `bar` here would cause <x>
+  end
+```
+
+Or
+
+```elixir
+  Api.read(:resource, bar: 10) # <- Adding `bar` here would cause <x>
+```
+
+**Additional context**
+Add any other context or screenshots about the feature request here.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,4 @@
+### Contributor checklist
+
+- [ ] Bug fixes include regression tests
+- [ ] Features include unit/acceptance tests

.github/workflows/elixir.yml

@@ -0,0 +1,14 @@
+name: CI
+on:
+  push:
+    tags:
+      - "v*"
+    branches: [main]
+  pull_request:
+    branches: [main]
+  workflow_call:
+jobs:
+  ash-ci:
+    uses: ash-project/ash/.github/workflows/ash-ci.yml@main
+    secrets:
+      HEX_API_KEY: ${{ secrets.HEX_API_KEY }}

README.md

@@ -80,7 +80,7 @@ paper_trail do
 end
 ```
 
-This will make your version resource have `foo` and `bar` attributes (they will still show up in `changes`), i.e 
+This will make your version resource have `foo` and `bar` attributes (they will still show up in `changes`), i.e
 ```elixir
 %ThingVersion{foo: "foo", bar: "bar", changes: %{"foo" => "foo", "bar" => "bar"}}
 ```

mix.exs

@@ -43,10 +43,19 @@ defmodule AshPaperTrail.MixProject do
   defp aliases do
     [
       sobelow: "sobelow --skip",
-      docs: ["docs", "ash.replace_doc_links"],
+      docs: [
+        "spark.cheat_sheets",
+        "docs",
+        "spark.replace_doc_links",
+        "spark.cheat_sheets_in_search"
+      ],
       credo: "credo --strict",
       "spark.formatter":
-        "spark.formatter --extensions AshPaperTrail.Resource,AshPaperTrail.Registry"
+        "spark.formatter --extensions AshPaperTrail.Resource,AshPaperTrail.Registry,AshPaperTrail.Api",
+      "spark.cheat_sheets_in_search":
+        "spark.cheat_sheets_in_search --extensions AshPaperTrail.Resource,AshPaperTrail.Registry,AshPaperTrail.Api",
+      "spark.cheat_sheets":
+        "spark.cheat_sheets --extensions AshPaperTrail.Resource,AshPaperTrail.Registry,AshPaperTrail.Api"
     ]
   end
 end