Enable CI

Open
#1 6 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
markdown, python
Domain
ci-cd, testing

Research direction

The issue mentions Markdown files, remark-lint, flake8, and pytest but no configuration files or exact checks. Start by inspecting the repository's CI and lint/test setup, then determine which checks apply to the Markdown and Python code blocks. Done means CI runs the agreed checks and reports failures, including doctests if any exist.

Written by the indexing model from the issue text.

Description

enhancement

We use remark-lint with plugins for md files.
Example: https://github.com/sobolevn/awesome-cryptography/

We can also use flake8 for code-blocks I guess.
And pytest to run doctests tests (if any).

Dominant language
No language data
Stars
78
Forks
6
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dry-python/functional-jargon-python

All issues in dry-python/functional-jargon-python

Similar issues

More DevOps issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.