Always go bleeding edge (#3)

.github/ISSUE_TEMPLATE/bug_report.md

@@ -22,7 +22,7 @@ A list of software versions where the bug is apparent, as detailed as possible:
 
 An ordered list of steps to replicate the bug:
 
-1. run `rebar3 ci`
+1. run `rebar3 as test ci`
 2. search for `...` in the error output
 3. look at file `...`
 

.github/workflows/ci.yml

@@ -52,3 +52,6 @@ jobs:
       - name: Continuous Integration
         run: |
           rebar3 as test ci
+
+      - name: Check if build left artifacts
+        run: git diff --exit-code

.gitignore

@@ -2,3 +2,4 @@ _build
 doc/
 erl_crash.dump
 rebar3.crashdump
+rebar.lock

CONTRIBUTING.md

@@ -20,8 +20,9 @@
 Bugs can be reported via
 [GitHub issues: bug report](https://github.com/arizona-framework/arizona_example/issues/new?template=bug_report.md).
 
-Some contributors and maintainers may be unpaid developers working on `arizona_example`, in their own time,
-with limited resources. We ask for respect and understanding, and will provide the same back.
+Some contributors and maintainers may be unpaid developers working on `arizona_example`, in their
+own time, with limited resources. We ask for respect and understanding, and will provide the same
+back.
 
 If your contribution is an actual bug fix, we ask you to include tests that, not only show the issue
 is solved, but help prevent future regressions related to it.
@@ -30,8 +31,8 @@ is solved, but help prevent future regressions related to it.
 
 Before requesting or implementing a new feature, do the following:
 
-- search, in existing [issues](https://github.com/arizona-framework/arizona_example/issues) (open or closed),
-whether the feature might already be in the works, or has already been rejected,
+- search, in existing [issues](https://github.com/arizona-framework/arizona_example/issues) (open or
+closed), whether the feature might already be in the works, or has already been rejected,
 - make sure you're using the latest software release (or even the latest code, if you're going for
 _bleeding edge_).
 
@@ -40,8 +41,8 @@ If this is done, open up a
 
 We may discuss details with you regarding the implementation, and its inclusion within the project.
 
-We try to have as many of `arizona_example`'s features tested as possible. Everything that a user can do,
-and is repeatable in any way, should be tested, to guarantee backwards compatible.
+We try to have as many of `arizona_example`'s features tested as possible. Everything that a user
+can do, and is repeatable in any way, should be tested, to guarantee backwards compatible.
 
 ## Submitting your changes
 

rebar.config

@@ -29,8 +29,6 @@
 
 {alias, [
     {ci, [
-        {unlock, "--all"},
-        {upgrade, "--all"},
         lint,
         {do, "default as test xref"},
         {do, "default as test dialyzer"},