docs: Switch to attribution of Mineiros (#15)

Author: gaima8

.github/CODEOWNERS

@@ -0,0 +1 @@
+* @gaima8

.pre-commit-config.yaml

@@ -7,7 +7,7 @@ repos:
       - id: end-of-file-fixer
       - id: mixed-line-ending
   - repo: https://github.com/antonbabenko/pre-commit-terraform
-    rev: v1.89.0
+    rev: v1.104.0
     hooks:
       - id: terraform_fmt
       - id: terraform_tflint

.terraform-docs.yaml

@@ -0,0 +1,5 @@
+formatter: "markdown document"
+settings:
+  hide-empty: true
+  lockfile: false
+  indent: 3

CHANGELOG.md

@@ -5,7 +5,11 @@ All notable changes to this project will be 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]
+## [0.19.2]
+
+### Features
+
+* Various updates ([#7](https://github.com/gaima8/terraform-github-repository/issues/7)) ([035f478](https://github.com/gaima8/terraform-github-repository/commit/035f4788abc91fbc0a81d3cb6bb7480fb1d137d1))
 
 ## [0.19.1]
 
@@ -419,7 +423,8 @@ Please review plans and report regressions and issues asap so we can improve doc
 - This is the initial release of our GitHub Repository module with support for
   creating and managing GitHub Repositories for Organizations.
 
-[unreleased]: https://github.com/mineiros-io/terraform-github-repository/compare/v0.19.0...HEAD
+[0.19.2]: https://github.com/gaima8/terraform-github-repository/compare/v0.19.1...v0.19.2
+[0.19.1]: https://github.com/gaima8/terraform-github-repository/compare/v0.19.0...v0.19.1
 [0.19.0]: https://github.com/mineiros-io/terraform-github-repository/compare/v0.18.0...v0.19.0
 [0.18.0]: https://github.com/mineiros-io/terraform-github-repository/compare/v0.17.0...v0.18.0
 [0.17.0]: https://github.com/mineiros-io/terraform-github-repository/compare/v0.16.2...v0.17.0

CONTRIBUTING.md

@@ -4,14 +4,15 @@ First and foremost, we’d like to express our gratitude to you for taking the t
 We welcome and appreciate any and all contributions via
 [Pull Requests] along the [GitHub Flow].
 
-1. [Open a GitHub issue](#open-a-github-issue)
-2. [Fork the repository on GitHub](#fork-the-repository-on-github)
-3. [Install the pre-commit hooks](#install-the-pre-commit-hooks)
-4. [Update the documentation](#update-the-documentation)
-5. [Update the tests](#update-the-tests)
-6. [Update the code](#update-the-code)
-7. [Create a pull request](#create-a-pull-request)
-8. [Merge and release](#merge-and-release)
+- [Contribution Guidelines](#contribution-guidelines)
+  - [Open a GitHub issue](#open-a-github-issue)
+  - [Fork the repository on GitHub](#fork-the-repository-on-github)
+  - [Install the pre-commit hooks](#install-the-pre-commit-hooks)
+  - [Update the documentation](#update-the-documentation)
+  - [Update the code](#update-the-code)
+  - [Create a pull request](#create-a-pull-request)
+  - [Merge and release](#merge-and-release)
+    - [Releases](#releases)
 
 ## Open a GitHub issue
 
@@ -42,18 +43,6 @@ We encourage you to update the documentation before writing any code (please see
 documentation stays up to date and allows you to think through the problem fully before you begin implementing any
 changes.
 
-## Update the tests
-
-We also recommend updating the automated tests before updating any code
-(see [Test Driven Development](https://en.wikipedia.org/wiki/Test-driven_development)).
-
-That means that you should add or update a test case, run all tests and verify
-that the new test fails with a clear error message and then start implementing
-the code changes to get that test to pass.
-
-The test folder in every repository will have documentation on how to run the
-tests locally.
-
 ## Update the code
 
 At this point, make your code changes and constantly test again your new test case to make sure that everything working
@@ -73,12 +62,16 @@ Please make sure to include the following:
 ## Merge and release
 
 The [CODEOWNERS] of the repository will review your code and provide feedback.
-If everything looks good, they will merge the code and release a new version while following the principles of [Semantic Versioning (SemVer)].
+If everything looks good, they will merge the code and potentially release a new version while following the principles of [Semantic Versioning (SemVer)].
+
+### Releases
+
+Release Please will create and update a pull request, which updates the CHANGELOG and prepares for a release. A [CODEOWNERS] will merge this at their discretion to action a release.
 
 <!-- References -->
 
-[pull requests]: https://github.com/mineiros-io/terraform-github-repository/pulls
-[pre-commit-file]: https://github.com/mineiros-io/terraform-github-repository/blob/main/.pre-commit-config.yaml
+[pull requests]: https://github.com/gaima8/terraform-github-repository/pulls
+[pre-commit-file]: https://github.com/gaima8/terraform-github-repository/blob/main/.pre-commit-config.yaml
 [github flow]: https://guides.github.com/introduction/flow/
 [codeowners]: https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
 [fork]: https://help.github.com/en/github/getting-started-with-github/fork-a-repo