docs: add missing docs

CONTRIBUTING.md

@@ -0,0 +1,55 @@
+# Contributing to Auth-tdd-client
+
+First of all, thanks for taking the time to contriute! 🎉🎉🎉🎉 👍
+
+The following is a seet of guidelines for contributing to Pydoautomator and its packages, which are hosted in the project's github. **These are mostly guidelines, not rules**. Use your best judgment, and feel free to propose changes to this document in a pull request.
+
+## How can I contribute
+
+______________________________
+
+### Reporting Bugs
+
+- Ensure the bug was not already reported by searching on GitHub under Issues.
+
+- If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
+
+### Suggesting Enhancement
+
+Enhancement suggestions are tracked as GitHub issues.
+
+- Use a clear and descriptive title for the issue to identify the suggestion.
+Provide a step-by-step description of the suggested enhancement in as many details as possible.
+- Provide specific examples to demonstrate the steps. Include copy/pasteable snippets which you use in those examples, as Markdown code blocks.
+- Describe the current behavior and explain which behavior you expected to see instead and why.
+- Explain why this enhancement would be useful to most Pydoautomator users and isn't something that can or should be implemented as a community package.
+
+### Your First Code Contribution
+
+Unsure where to begin contributing to Pydoautomator? You can start by looking through these `good-first-issue` and `help-wanted` issues.
+
+
+- **Beginner issues** - issues which should only require a few lines of code, and a test or two.
+- **Help wanted issues** - issues which should be a bit more involved than beginner issues.
+
+Both issue lists are sorted by total number of comments. While not perfect, number of comments is a reasonable proxy for impact a given change will have.
+
+## Styleguides
+
+### Git Commit Messages
+
+We follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/)
+
+A good tool for following Conventional Commits is [commitizen](https://commitizen-tools.github.io/commitizen/). We recommend you to check it.
+
+### Code
+
+For now we follow `PEP 8`. Please feel free to suggest anything different.
+
+### Documentation
+
+**Public objects:** Sphinx docstring (optional)
+**Private objects:** Sphinx docstring (optional)
+
+## Pull Requests
+Submit your PR, all checks must pass. Code will be reviewed.

LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2023 Christian Eland
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.