Metadata-Version: 2.1
Name: mk
Version: 2.1.0
Summary: mk
Author-email: Sorin Sbarnea <sorin.sbarnea@gmail.com>
License: MIT
Project-URL: homepage, https://github.com/pycontribs/mk
Project-URL: repository, https://github.com/pycontribs/mk
Project-URL: changelog, https://github.com/pycontribs/mk/releases
Keywords: mk
Classifier: Development Status :: 5 - Production/Stable
Classifier: Environment :: Console
Classifier: Intended Audience :: Developers
Classifier: Intended Audience :: Information Technology
Classifier: Intended Audience :: System Administrators
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: MacOS
Classifier: Operating System :: POSIX
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.8
Classifier: Programming Language :: Python :: 3.9
Classifier: Programming Language :: Python :: 3.10
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3 :: Only
Classifier: Programming Language :: Python
Classifier: Topic :: Software Development :: Quality Assurance
Classifier: Topic :: Software Development :: Testing
Classifier: Topic :: Utilities
Requires-Python: >=3.8
Description-Content-Type: text/markdown
License-File: LICENSE
Requires-Dist: GitPython
Requires-Dist: diskcache (>=5.2.1)
Requires-Dist: blessings
Requires-Dist: build (>=0.3.1.post1)
Requires-Dist: click (>=7.1.2)
Requires-Dist: colorama
Requires-Dist: importlib-metadata
Requires-Dist: pip (>=21.0.1)
Requires-Dist: pluggy
Requires-Dist: pygments
Requires-Dist: pyyaml
Requires-Dist: rich (>=9.0)
Requires-Dist: shellingham
Requires-Dist: subprocess-tee (>=0.3.1)
Requires-Dist: twine (>=3.4.1)
Requires-Dist: typer
Provides-Extra: docs
Requires-Dist: cairosvg (>=2.6.0) ; extra == 'docs'
Requires-Dist: markdown-exec (>=1.3.0) ; extra == 'docs'
Requires-Dist: mkdocs-autorefs ; extra == 'docs'
Requires-Dist: mkdocs-gen-files (>=0.4.0) ; extra == 'docs'
Requires-Dist: mkdocs-htmlproofer-plugin (>=0.10.2) ; extra == 'docs'
Requires-Dist: mkdocs-material-extensions (>=1.1.1) ; extra == 'docs'
Requires-Dist: mkdocs-material (>=9.0.13) ; extra == 'docs'
Requires-Dist: mkdocs (>=1.4.2) ; extra == 'docs'
Requires-Dist: pillow (>=9.4.0) ; extra == 'docs'
Requires-Dist: pipdeptree (>=2.4.0) ; extra == 'docs'
Requires-Dist: pymdown-extensions (>=9.9.2) ; extra == 'docs'
Provides-Extra: test
Requires-Dist: pytest ; extra == 'test'
Requires-Dist: pytest-benchmark ; extra == 'test'
Requires-Dist: pytest-plus ; extra == 'test'
Requires-Dist: tox (>=4.0.0) ; extra == 'test'

# Documentation of mk tool

`mk` is a CLI tool that aims to ease contribution to any open-source project
by hiding repository implementation details from the casual contributor.
With it, you can contribute without having to know all the build
and testing tools that the project team already uses, which often have
strange requirements.

If you ever asked yourself one of the below questions, probably you would
want to try `mk` and if it can help you

* How do I run tests locally?
* Which are the test suites I can run?
* Is my change ready to be reviewed?
* How can I propose a change for review?

Run `mk` inside any cloned repository to display which options you have. No
configuration file is needed as the tool will look for
common tools used by the repository and expose their commands.

`mk` is inspired by the tools listed below, but it does not aim to replace them.

* [make](https://www.gnu.org/software/make/)
* [waf](https://gitlab.com/ita1024/waf)
* [tox](https://github.com/tox-dev/tox/) and [nox](https://nox.thea.codes/en/stable/)
* [npm](https://www.npmjs.com/) and [yarn](https://yarnpkg.com/)
* [pre-commit](https://pre-commit.com/)

## Installation

We recommend using [`pipx`](https://pipxproject.github.io/pipx/) to install
`mk` in order to avoid potential dependency conflicts. You can use
`pip3 install mk` as well.

```shell
pipx install mk
```

## Run it

![](images/mk-social-preview.png)

## How it works

`mk` inspects the current core repository and detects build tools used
by the project, like pre-commit, tox, npm and exposes their commands to
the user in a **predictable** way.

For example, you should be able to lint any code repository running only
`mk lint`, regardless of author preference for picking one way to execute
them or another.

Be assured that `mk` does not make use of AI to guess what needs to
run. As most projects use relatively similar patterns, it is easy to identify
the one to execute.

At this moment, if two tools expose the same command name, the tool will add
a number to its name. In the future, we may decide to either chain them under
a single name or allow some tools to shadow others and avoid duplicates.

## What are the main benefits

One of the benefits of `mk` is that it should reduce the amount of
how-to-contribute documentation the author needs to write.

A considerable amount of maintainer effort can go into producing documentation
that makes it easier for someone to make a contribution to a project.

Some projects are less affected than others. That is usually related to
how well do the potential contributors know the practices used by the
project. Still, if your project has a wide range of uses, you will quickly
discover that newbie contributors may hit a knowledge wall. Such a barrier will
likely prevent most of them from becoming active contributors. The remaining
ones will flood the project with questions, distracting other maintainers from
doing more advanced tasks.

Unless you want to deter contributions, you should plan to make it as easy as
possible for people to contribute. That is one area where `mk` aims to help.

## Using mk to propose changes to projects

Instead of writing long list of tasks to follow, we can use a tool that
tells him what to do next. For example, `mk` has a build-in command named
`up(load)` that aims to ease preparing a local change from being
proposed to the project.

This command detects if it should use GitHub workflow or
Gerrit and will run the appropriate commands for opening or updating a CR/PR. Users
will be allowed to upload a change only after passing the minimal set of local
tests, preventing noisy mistakes or clog CI/CD pipelines.

In addition to linting, it will also check that the repository is
not in dirty status or that the testing did not leave untracked files on disk.

## Planned features

* Allow command aliases like git. If you type `mk l` it should directly run
  lint unless there is another command starting with `l`. (#19)
* Persistent state of each command run - This means that it will know if a
  specific command was run and if it failed or not. The state would be linked
  to the repository state, so modifying a tracked file would reset the state
  to be unknown. (#20)
* Configuration file where additional actions can be added. (#21)
* Dependencies between commands. While some tools support dependencies,
  many do not. You should be able to declare that a specific command would
  run only after another one already passed. (#22)
* Ability to generate CI/CD pipelines so the user would spend less time writing
  non-portable configuration. (#23)
