clean_git_history_lib 0.1.1

A Git history linter to ensure it stays clean for those who prefer rebasing and fast-forwarding compared to merge and squash commits.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

# Clean Git History Library
[![Documentation](https://docs.rs/clean_git_history_lib/badge.svg)](https://docs.rs/clean_git_history_lib) [![crates.io](https://img.shields.io/crates/v/clean_git_history_lib)](https://crates.io/crates/clean_git_history_lib) [![pipeline status](https://gitlab.com/DeveloperC/clean_git_history/badges/main/pipeline.svg)](https://gitlab.com/DeveloperC/clean_git_history/-/commits/main) [![Conventional Commits](https://img.shields.io/badge/Conventional%20Commits-1.0.0-yellow.svg)](https://conventionalcommits.org) [![License: AGPL v3](https://img.shields.io/badge/License-AGPLv3-blue.svg)](https://www.gnu.org/licenses/agpl-3.0)

A Git history linter Library to ensure it stays clean for those who prefer rebasing and fast-forwarding compared to merge and squash commits.


## Content
 * [Usage](#usage)
   + [Usage - Logging](#usage-logging)
 * [Issues/Feature Requests](#issuesfeature-requests)


## Usage


### Usage - Logging
The crate `log` is used to provide logging.
The environment variable `RUST_LOG` can be used to set the logging level.
See [https://crates.io/crates/log](https://crates.io/crates/log) for more detailed documentation.


## Issues/Feature Requests
To report an issue or request a new feature use [https://gitlab.com/DeveloperC/clean_git_history/-/issues](https://gitlab.com/DeveloperC/clean_git_history/-/issues).