-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added documentation including changelog, contributing and readme
- Loading branch information
Showing
4 changed files
with
302 additions
and
116 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,14 @@ | ||
# Changelog | ||
|
||
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). | ||
|
||
## [1.0.0] - 2024-11-12 | ||
|
||
### Added | ||
- Initial release with core functionality | ||
- Authentication management (SSH, GitHub) | ||
- Configuration management | ||
- Hook management |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,54 @@ | ||
# Contributing to deadlight-guardian | ||
|
||
We love your input! We want to make contributing as easy and transparent as possible. | ||
|
||
## Development Process | ||
|
||
1. Fork the repo and create your branch from `main`. | ||
2. If you've added code that should be tested, add tests. | ||
3. Update the documentation. | ||
4. Ensure the test suite passes. | ||
5. Make sure your code lints. | ||
6. Issue a pull request. | ||
|
||
## Any contributions you make will be under the MIT License | ||
When you submit code changes, your submissions are understood to be under the same [MIT License](LICENSE) that covers the project. | ||
|
||
## Report bugs using GitHub's [issue tracker] | ||
We use GitHub issues to track public bugs. Report a bug by [opening a new issue](). | ||
|
||
## Write bug reports with detail, background, and sample code | ||
|
||
**Great Bug Reports** tend to have: | ||
|
||
- A quick summary and/or background | ||
- Steps to reproduce | ||
- Be specific! | ||
- Give sample code if you can. | ||
- What you expected would happen | ||
- What actually happens | ||
- Notes (possibly including why you think this might be happening, or stuff you tried that didn't work) | ||
|
||
## Development Setup | ||
|
||
1. Clone the repository | ||
2. Create a virtual environment: `python -m venv venv` | ||
3. Activate the environment: `source venv/bin/activate` | ||
4. Install dependencies: `pip install -e ".[dev]"` | ||
5. Install pre-commit hooks: `guardian hooks install` | ||
|
||
## Testing | ||
|
||
```bash | ||
# Run all tests | ||
pytest | ||
|
||
# Run with coverage | ||
pytest --cov=guardian | ||
``` | ||
|
||
## Pull Request Process | ||
|
||
1. Update the README.md with details of changes if needed. | ||
2. Update the CHANGELOG.md with notes on your changes. | ||
3. The PR will be merged once you have the sign-off of another developer. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.