behave-cucumber-parser 1.1.0__tar.gz

behave_cucumber_parser-1.1.0/.gitignore

@@ -0,0 +1,3 @@
+.*.venv/
+bin/
+behave.ini

behave_cucumber_parser-1.1.0/.gitlab-ci.yml

@@ -0,0 +1,82 @@
+
+stages:
+  - build
+  - test
+  - deploy
+  - cleanup
+  - release
+
+include:
+  # Build documentation
+  - component: $CI_SERVER_FQDN/pm-virutallab/workflow/automatic-docu-generation/docuPipeline@1.2.0
+    inputs:
+      # Sphinx arguments
+      source: "."
+      output: "bin"
+      # Environment arguments
+      pipDependencies:
+        - "-r dependencies/docu.requirements.txt"
+      # Pipeline settings
+      buildStage: "build"
+      deployStage: "deploy"
+      needs: []
+      tags:
+        - "saas-linux-small-amd64"
+      expireIn: 1 week
+
+  # Build, test, deploy and cleanup the python package
+  # Uses the "build"/"buildApt" environment declared in pyproject.toml
+  - component: $CI_SERVER_FQDN/pm-virutallab/workflow/python-packaging/pythonPackagePipeline@1.1.0
+    inputs:
+      # Build arguments
+      source: "."
+      output: "bin/dist"
+      buildEnvironment: "build"
+      # Test arguments
+      testEnvironments:
+        - test
+      testReportsDirectory: bin/test/reports
+      # Deploy arguments
+      pypiDeploy: true
+      pypiTrustedPublishing: true
+      # Pipeline settings
+      buildJob: "build-python-package"
+      testJobPrefix: "test-python-package"
+      deployJob: "deploy-python-package"
+      pypiDeployJob: "deploy-python-package-pypi"
+      cleanupJob: "cleanup-python-package"
+      buildStage: "build"
+      testStage: "test"
+      deployStage: "deploy"
+      cleanupStage: "cleanup"
+      needs: []
+      tags:
+        - "saas-linux-small-amd64"
+      expireIn: 1 week
+
+# If the pipeline is for a new tag with a semantic version, and all previous
+# jobs succeed, create the release.
+create-release:
+  stage: release
+  image: registry.gitlab.com/gitlab-org/cli:latest
+  before_script: []
+  script: echo "Creating release $CI_COMMIT_TAG"
+  needs:
+    - build-docu-pdf
+    - deploy-docu-pages-tag
+    - build-python-package
+  rules:
+    - if: $CI_COMMIT_TAG
+  release:
+    tag_name: $CI_COMMIT_TAG
+    description: "Release $CI_COMMIT_TAG of $CI_PROJECT_PATH"
+    assets:
+      links:
+        - name: Online Documentation
+          url: $deploy_docu_pages_tag_url
+        - name: PDF Documentation
+          url: $build_docu_pdf_url
+        - name: Python binary package
+          url: $build_python_package_whl_url
+        - name: Source distribution
+          url: $build_python_package_sdist_url

behave_cucumber_parser-1.1.0/LICENSE

@@ -0,0 +1,30 @@
+Copyright (c) 2026, Paul Markstädter
+
+Redistribution and use in source and binary forms, with or without
+modification, are permitted provided that the following conditions are met:
+
+1. Redistributions of source code must retain the above copyright notice,
+   this list of conditions and the following disclaimer.
+
+2. Redistributions in binary form must reproduce the above copyright notice,
+   this list of conditions and the following disclaimer in the documentation
+   and/or other materials provided with the distribution.
+
+THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS"
+AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
+LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
+CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
+SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
+CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
+ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
+POSSIBILITY OF SUCH DAMAGE.
+
+---
+
+This project also contains code adapted from behave
+(https://github.com/behave/behave), used and modified under its own
+BSD-2-Clause license — see src/patches/BEHAVE_LICENSE.md for the full
+upstream notice and src/patches/ for what was adapted and why.

behave_cucumber_parser-1.1.0/PKG-INFO

@@ -0,0 +1,39 @@
+Metadata-Version: 2.5
+Name: behave_cucumber_parser
+Version: 1.1.0
+Summary: Parses feature files with gherkin-official, cucumber's own reference Gherkin parser, instead of behave's built-in parser, so upcoming Gherkin changes such as Markdown with Gherkin can be adopted before behave supports them natively.
+Project-URL: Homepage, https://gitlab.com/pm-virutallab/workflow/behave-cucumber-parser
+Project-URL: Repository, https://gitlab.com/pm-virutallab/workflow/behave-cucumber-parser
+Project-URL: Documentation, https://behave-cucumber-parser-c2df5d.gitlab.io/
+Project-URL: Issues, https://gitlab.com/pm-virutallab/workflow/behave-cucumber-parser/-/work_items
+Author-email: Paul Markstädter <paul.markstaedter.git@mailbox.org>
+Maintainer-email: Paul Markstädter <paul.markstaedter.git@mailbox.org>
+License-Expression: BSD-2-Clause
+License-File: LICENSE
+License-File: src/patches/BEHAVE_LICENSE.md
+Requires-Dist: behave>=1.3.3
+Requires-Dist: gherkin-official>=41.0.0
+Provides-Extra: build
+Requires-Dist: build>=1.5.0; extra == 'build'
+Requires-Dist: hatch-requirements-txt>=0.4.1; extra == 'build'
+Requires-Dist: hatchling>=1.29.0; extra == 'build'
+Requires-Dist: versioningit>=3.3.0; extra == 'build'
+Provides-Extra: buildapt
+Requires-Dist: git; extra == 'buildapt'
+Requires-Dist: python3; extra == 'buildapt'
+Requires-Dist: python3-venv; extra == 'buildapt'
+Provides-Extra: docu
+Requires-Dist: myst-parser>=5.1.0; extra == 'docu'
+Requires-Dist: sphinx-autobuild>=2025.8.25; extra == 'docu'
+Requires-Dist: sphinx-book-theme>=1.2.0; extra == 'docu'
+Requires-Dist: sphinx>=9.1.0; extra == 'docu'
+Requires-Dist: versioningit>=3.3.0; extra == 'docu'
+Provides-Extra: docuapt
+Requires-Dist: texlive-full; extra == 'docuapt'
+Provides-Extra: runtime
+Requires-Dist: behave>=1.3.3; extra == 'runtime'
+Requires-Dist: gherkin-official>=41.0.0; extra == 'runtime'
+Provides-Extra: runtimeapt
+Provides-Extra: test
+Requires-Dist: behave>=1.3.3; extra == 'test'
+Provides-Extra: testapt

behave_cucumber_parser-1.1.0/README.md

@@ -0,0 +1,66 @@
+# Behave Cucumber Parser
+
+[![pipeline status](https://img.shields.io/gitlab/pipeline-status/pm-virutallab%2Fworkflow%2Fbehave-cucumber-parser.png)](https://gitlab.com/pm-virutallab/workflow/behave-cucumber-parser/-/commits/main)
+[![Latest Release](https://img.shields.io/gitlab/v/release/pm-virutallab%2Fworkflow%2Fbehave-cucumber-parser.png)](https://gitlab.com/pm-virutallab/workflow/behave-cucumber-parser/-/releases)
+[![License: BSD-2-Clause](https://img.shields.io/badge/License-BSD--2--Clause-blue.png)](LICENSE)
+
+Parses feature files with [gherkin-official](https://pypi.org/project/gherkin-official/),
+cucumber's own reference Gherkin parser, instead of behave's built-in
+parser, so upcoming Gherkin changes such as
+[Markdown with Gherkin](https://github.com/cucumber/gherkin/blob/main/MARKDOWN_WITH_GHERKIN.md)
+can be adopted before behave supports them natively.
+
+## Project Structure
+
+```md
+project/
+├── dependencies/              # Python/Debian dependency lists, one pair per environment
+│   ├── build.requirements.txt / build.apt.requirements
+│   ├── docu.requirements.txt / docu.apt.requirements
+│   ├── runtime.requirements.txt / runtime.apt.requirements
+│   └── test.requirements.txt / test.apt.requirements
+├── docu/                      # Documentation source files (Sphinx / Markdown)
+│   ├── devEnvironment.md      # How to set up the local development environment
+│   ├── features.md            # Feature overview (pulls in files from features/)
+│   ├── patches.md             # What behave internals are overridden, and why
+│   └── updateFromTemplate.md  # How to pull updates from the project template
+├── features/                  # Gherkin feature files — machine-readable requirements
+│   ├── MarkdownWithGherkin.feature.md
+│   ├── test_behave.ini        # behave preset for the "test" environment
+│   ├── test_environment.py
+│   └── test_steps/
+├── src/                        # Python package source, packaged as behave_cucumber_parser
+│   ├── adapter/                # Cucumber-Gherkin AST -> behave model conversion
+│   └── patches/                # behave internals overrides + install.py, see docu/patches.md
+├── setup.env.sh                # Install an environment's Python + Debian dependencies
+├── setup.debian.sh / setup.python.sh / setup.base.sh
+├── .gitignore
+├── .gitlab-ci.yml            # CI/CD pipeline: build docs, package, test, deploy, cleanup, release
+├── conf.py                   # Sphinx documentation configuration
+├── index.rst                 # Sphinx documentation root (table of contents)
+├── LICENSE                   # This project's own license (BSD-2-Clause)
+└── pyproject.toml            # Project metadata, versioning and dependency configuration
+```
+
+## Development
+
+- [Set up the development environment](docu/devEnvironment.md)
+- [Features](docu/features.md) describing functionality of this project
+- [Patches](docu/patches.md) describing which behave internals are overridden, and why
+- [Update from template](docu/updateFromTemplate.md) when the template changes
+- The project is packaged and released via the
+  [pythonPackagePipeline](https://gitlab.com/pm-virutallab/workflow/python-packaging)
+  GitLab CI/CD Catalog component, wired up in [.gitlab-ci.yml](.gitlab-ci.yml)
+
+## License
+
+This project is licensed under [BSD-2-Clause](LICENSE).
+
+It depends on [gherkin-official](https://pypi.org/project/gherkin-official/)
+(MIT license) as its underlying Cucumber/Gherkin parser, used unmodified as
+a regular dependency — no source is copied from it.
+
+It also adapts small, modified pieces of [behave](https://github.com/behave/behave)
+itself (also BSD-2-Clause) — see [Patches](docu/patches.md) for what and why,
+and [`src/patches/BEHAVE_LICENSE.md`](src/patches/BEHAVE_LICENSE.md) for the
+full upstream notice.

behave_cucumber_parser-1.1.0/conf.py

@@ -0,0 +1,60 @@
+# Configuration file for the Sphinx documentation builder.
+#
+# For the full list of built-in configuration values, see the documentation:
+# https://www.sphinx-doc.org/en/master/usage/configuration.html
+
+# -- Project information -----------------------------------------------------
+# https://www.sphinx-doc.org/en/master/usage/configuration.html#project-information
+
+project = 'Behave Cucumber Parser'
+copyright = '2026, Paul Markstädter'
+author = 'Paul Markstädter'
+
+# Load version from git tag
+from pathlib import Path
+import versioningit
+release = versioningit.get_version(Path(__file__).parent)
+version = '.'.join(release.split('.')[:2])
+
+# -- General configuration ---------------------------------------------------
+# https://www.sphinx-doc.org/en/master/usage/configuration.html#general-configuration
+
+extensions = [
+    'myst_parser',
+]
+
+# Generate heading anchors (e.g. #dependencies-feature) so docu/*.md files
+# can cross-reference each other's sections with plain markdown links.
+myst_heading_anchors = 3
+
+source_suffix = {
+    '.rst': 'restructuredtext',
+    '.txt': 'markdown',
+    '.md': 'markdown',
+}
+
+# templates_path = ['_templates']
+exclude_patterns = [
+    'bin',
+    '.*.venv',
+    'Thumbs.db',
+    '.DS_Store',
+    'dependencies',
+    ]
+
+
+
+# -- Options for HTML output -------------------------------------------------
+# https://www.sphinx-doc.org/en/master/usage/configuration.html#options-for-html-output
+
+import os
+
+html_theme = 'sphinx_book_theme'
+html_static_path = ['_static']
+html_theme_options = {
+    "repository_provider": "gitlab",
+    "repository_url": os.environ.get("CI_PROJECT_URL",
+        "Provided in pipeline by $CI_PROJECT_URL (https://docs.gitlab.com/ci/variables/predefined_variables/)"),
+    "use_repository_button": True,
+    "use_issues_button": True,
+}

behave_cucumber_parser-1.1.0/dependencies/build.apt.requirements

@@ -0,0 +1,6 @@
+# Debian packages needed to build and package the project.
+# Installed via the "buildApt" environment (see ../pyproject.toml optional-dependencies).
+
+git
+python3
+python3-venv

behave_cucumber_parser-1.1.0/dependencies/build.requirements.txt

@@ -0,0 +1,10 @@
+# Python packages needed to build and package the project.
+# Installed via the "build" environment (see ../pyproject.toml optional-dependencies).
+
+# Dependencies for packaging
+build >= 1.5.0
+hatchling >= 1.29.0
+versioningit >= 3.3.0
+hatch-requirements-txt >= 0.4.1
+
+# Dependencies of build scripts

behave_cucumber_parser-1.1.0/dependencies/docu.apt.requirements

@@ -0,0 +1,6 @@
+# Debian packages needed to generate documentation.
+# Installed via the "docuApt" environment (see ../pyproject.toml optional-dependencies).
+# Only required to build the PDF via Sphinx's LaTeX builder (see
+# ../docu/devEnvironment.md); the HTML build needs no system packages.
+
+texlive-full

behave_cucumber_parser-1.1.0/dependencies/docu.requirements.txt

@@ -0,0 +1,15 @@
+# Python packages needed to generate documentation.
+# Installed via the "docu" environment (see ../pyproject.toml optional-dependencies).
+
+# sphinx
+Sphinx >= 9.1.0
+sphinx-autobuild >= 2025.8.25
+
+#utils
+versioningit >= 3.3.0
+
+# extensions
+myst-parser >= 5.1.0
+
+# Themes
+sphinx-book-theme >= 1.2.0

behave_cucumber_parser-1.1.0/dependencies/runtime.apt.requirements

@@ -0,0 +1,3 @@
+# Debian packages needed to run the project.
+# Installed via the "runtimeApt" environment (see ../pyproject.toml optional-dependencies).
+# Currently empty: no system packages are required at runtime.

behave_cucumber_parser-1.1.0/dependencies/runtime.requirements.txt

@@ -0,0 +1,7 @@
+# Python packages needed to run the project.
+# Always installed with the package (see ../pyproject.toml
+# [tool.hatch.metadata.hooks.requirements_txt]), and also available as
+# the "runtime" environment for local setup.
+
+behave >= 1.3.3
+gherkin-official >= 41.0.0

behave_cucumber_parser-1.1.0/dependencies/test.apt.requirements

@@ -0,0 +1,3 @@
+# Debian packages needed to test the package.
+# Installed via the "testApt" environment (see ../pyproject.toml optional-dependencies).
+# Currently empty: no system packages are required for testing.

behave_cucumber_parser-1.1.0/dependencies/test.requirements.txt

@@ -0,0 +1,5 @@
+# Python packages needed to test the package.
+# Installed via the "test" environment (see ../pyproject.toml optional-dependencies).
+
+# Test framework
+behave >= 1.3.3

behave_cucumber_parser-1.1.0/docu/devEnvironment.md

@@ -0,0 +1,129 @@
+# Development environment
+
+To set up the development environment for this project, follow these steps:
+
+## Prerequisites
+
+- Git and python installed on your local machine
+- A GitLab account with access to this repository
+- A text editor or IDE of your choice
+
+## Clone the repository
+
+```sh
+git clone https://gitlab.com/pm-virutallab/workflow/behave-cucumber-parser.git
+cd <repository-directory>
+```
+
+## Set up an environment
+
+Each stage of the project (building, running, testing, building the
+documentation, ...) has its own environment, declared in
+[pyproject.toml](../pyproject.toml) under
+`tool.hatch.metadata.hooks.requirements_txt.optional-dependencies`. Every
+environment `<name>` has two entries:
+
+- `<name>`: PyPI package dependencies, listed in
+  `dependencies/<name>.requirements.txt`
+- `<name>Apt`: Debian package dependencies, listed in
+  `dependencies/<name>.apt.requirements`
+
+Set up any declared environment with a single command, which installs
+both its Python and Debian dependencies into a dedicated `.<name>.venv`
+virtual environment:
+
+```sh
+source ./setup.env.sh <name>
+```
+
+For example, to set up the environment used for building the
+documentation:
+
+```sh
+source ./setup.env.sh docu
+```
+
+Debian and Python dependencies can also be installed separately:
+
+```sh
+# Install deb packages (requires sudo)
+source ./setup.debian.sh <name>
+# Install pypi packages
+source ./setup.python.sh <name>
+```
+
+Both [setup.debian.sh](../setup.debian.sh) and
+[setup.python.sh](../setup.python.sh) build on top of
+[setup.base.sh](../setup.base.sh), which creates/activates the
+`.<name>.venv` virtual environment and installs the `build` package used
+to discover an environment's dependencies from `pyproject.toml` via
+`python -m build --metadata`.
+
+## Build the package
+
+```sh
+source ./setup.env.sh build
+python -m build --outdir bin/dist .
+```
+
+The wheel and source distribution are written to `bin/dist`.
+
+## Run tests
+
+```sh
+source ./setup.env.sh test
+cp -f features/test_behave.ini behave.ini
+behave
+```
+
+JUnit reports are written to `bin/test/reports`. See
+[Features](features.md) for how feature files, environments and behave
+presets relate to each other.
+
+## Generate the documentation
+
+```sh
+source ./setup.env.sh docu
+sphinx-build . bin
+```
+
+Or, to rebuild automatically as files change and serve a live preview:
+
+```sh
+sphinx-autobuild . bin
+```
+
+The generated HTML is written to `bin`.
+
+## Generate the PDF documentation
+
+Building the PDF additionally requires a LaTeX distribution, installed
+via the `docuApt` entry of the `docu` environment (see
+[dependencies/docu.apt.requirements](../dependencies/docu.apt.requirements)):
+
+```sh
+source ./setup.env.sh docu
+sphinx-build -M latexpdf . bin
+```
+
+The generated PDF is written to `bin/latex`.
+
+## Create a release
+
+The version is derived from the most recent git tag in
+[semantic version format](https://semver.org/) (e.g. `1.0.0`) via
+[versioningit](https://versioningit.readthedocs.io), configured in
+[pyproject.toml](../pyproject.toml) under `tool.hatch.version`. Tagging
+a commit and pushing the tag both cuts the release and triggers it:
+
+```sh
+git tag 1.0.0
+git push origin 1.0.0
+```
+
+Pushing the tag runs the full pipeline (`.gitlab-ci.yml`) against that
+commit, building the package and documentation with that exact version.
+Once every job succeeds, `create-release` publishes a GitLab release
+for the tag with the HTML docs, PDF docs, wheel and sdist attached as
+release assets, in addition to `deploy-python-package` uploading the
+package to the registry as on every pipeline.

behave_cucumber_parser-1.1.0/docu/features.md

@@ -0,0 +1,78 @@
+# Features
+
+Following features describe the functionality of this project.
+Feature files are written in [Gherkin](https://cucumber.io/docs/gherkin/) syntax.
+[behave](https://behave.readthedocs.io/en/stable/) is used to test the project against the features.
+Therefore the steps are implemented per environment under
+`features/<name>_steps/`, e.g. [test_steps](../features/test_steps/).
+
+- [Features](#features)
+  - [Feature List](#feature-list)
+  - [Presets](#presets)
+  - [Tagging](#tagging)
+    - [Deprecated](#deprecated)
+    - [Environment test](#environment-test)
+    - [Not Implemented](#not-implemented)
+    - [Manual](#manual)
+    - [Work in progress](#work-in-progress)
+
+## Feature List
+
+% In a plain Markdown preview (GitHub, editors, ...) this is just a fenced  
+% code block. Built with Sphinx, it expands into a live, linked table of  
+% contents listing every `*.feature.md` file in `features/`.  
+
+```{toctree}
+:glob:
+../features/*.feature
+```
+
+## Presets
+
+Each environment declared in `pyproject.toml` (see
+[Set up an environment](devEnvironment.md#set-up-an-environment)) ships its own behave
+configuration preset, named `features/<name>_behave.ini`. Copy the desired
+environment's preset to the repository's top directory to run `behave` for
+that environment only:
+
+```sh
+cp -f features/<name>_behave.ini behave.ini
+behave
+```
+
+- [test_behave.ini](../features/test_behave.ini): Runs scenarios tagged `@env:test`.
+
+## Tagging
+
+The features, rules or scenarios may be tagged, to describe when they have to be executed.
+This sections describes which tags are used and when to use them.
+
+### Deprecated
+
+The `@deprecated` tag marks parts, which where tested / supported in the past and are not guaranteed to work in future.
+
+### Environment test
+
+The `@env:test` tag marks parts, which are tested in the `test` environment.
+The apt and pypi packages this environment depends on are described in [pyproject.toml](../pyproject.toml):
+
+```toml
+[tool.hatch.metadata.hooks.requirements_txt.optional-dependencies]
+test = ["dependencies/test.requirements.txt"]
+testApt = ["dependencies/test.apt.requirements"]
+```
+
+### Not Implemented
+
+The `@not-implemented` tag marks parts which are already described, but not implemented.
+This could be used to write tests, before the implementation of the features.
+
+### Manual
+
+The `@manual` tag marks parts, which can't be tested automatically at the moment.
+They have more documentation purpose.
+
+### Work in progress
+
+The `@wip` tag is used to mark sections, the developer is currently implementing or investigating.
+This makes it simpler to test the current work, to get faster results.

behave_cucumber_parser-1.1.0/docu/patches.md

@@ -0,0 +1,35 @@
+# Patches
+
+This project overrides three pieces of `behave`'s own internals, so that
+`behave` runs feature files through the `gherkin` package's Cucumber parser
+instead of its own, and so it discovers `*.feature.md` files — `behave` only
+looks for `*.feature` files and parses with its own parser by default.
+
+| Patch                                                                      | Overrides                                                                | Source                                   |
+| -------------------------------------------------------------------------- | ------------------------------------------------------------------------ | ---------------------------------------- |
+| [`parse_features`](../src/patches/parse_features.md)                       | `behave.runner_util.parse_features()` / `behave.runner.parse_features()` | Original code, not adapted from `behave` |
+| [`collect_feature_locations`](../src/patches/collect_feature_locations.md) | `behave.runner_util.collect_feature_locations()`                         | Adapted from `behave`                    |
+| [`setup_paths`](../src/patches/setup_paths.md)                             | `behave.runner.Runner.setup_paths()`                                     | Adapted from `behave`                    |
+
+`collect_feature_locations` and `setup_paths` are copied-and-modified
+`behave` source, distributed under `behave`'s BSD-2-Clause license — see
+[`BEHAVE_LICENSE.md`](../src/patches/BEHAVE_LICENSE.md) for the
+full upstream notice.
+
+All three are applied at interpreter startup by
+[`pth/behave_cucumber_parser.pth`](../pth/behave_cucumber_parser.pth) via
+[`install.py`](../src/patches/install.md).
+
+% In a plain Markdown preview this is just a fenced code block. Built with  
+% Sphinx, it expands into a live, linked table of contents listing every  
+% `.md` doc in `src/patches/`.
+
+```{toctree}
+:glob:
+
+../src/patches/*
+```
+
+The actual Cucumber-Gherkin-AST-to-`behave`-model conversion that
+`parse_features` calls into lives in `src/adapter/` — also original code,
+not adapted from `behave`.

behave_cucumber_parser-1.1.0/docu/updateFromTemplate.md

@@ -0,0 +1,47 @@
+# Updating from template
+
+This project is created from a template and can receive updates when the template itself changes.
+This is done by adding the template repository as a Git remote called `template`.
+
+## Setup
+
+Add the template repository as a remote:
+
+```sh
+git remote add template <template-repo-url>
+```
+
+## Pulling Template Updates
+
+```sh
+git branch template/update
+git switch template/update
+git fetch template
+git merge template/main
+```
+
+Git will merge only the lines that changed in the template, so customizations like
+replaced placeholders and project-specific content are preserved where there is no conflict.
+
+## Resolving Conflicts
+
+Conflicts occur where both the template and your project modified the same lines.
+Git will mark the affected files:
+
+```diff
+<<<<<<< HEAD
+your project's version
+=======
+template's updated version
+>>>>>>> template/main
+```
+
+Resolve each conflict by editing the file to the desired result, then commit and push changes.
+
+## What to Expect
+
+- **Replaced placeholders** (e.g. `<<PROJECT_NAME>>`) are not re-introduced as long as you
+  have already replaced them — only changed lines propagate.
+- **Files you deleted** (e.g. removed feature files) will not reappear unless the template
+  also modified those files, in which case Git raises a conflict to let you decide.
+- **New files** added to the template are merged in automatically without conflict.

behave_cucumber_parser-1.1.0/features/.markdownlint.jsonc

@@ -0,0 +1,20 @@
+{
+  // Scoped to features/: these files are Markdown with Gherkin
+  // (https://github.com/cucumber/gherkin/blob/main/MARKDOWN_WITH_GHERKIN.md),
+  // not prose Markdown, so the rules below don't apply and must stay
+  // disabled here rather than via inline markdownlint-disable comments —
+  // an HTML comment as the first line breaks the Gherkin-in-Markdown parser
+  // (it gets consumed as the Feature line instead of the real "# Feature:").
+
+  // First line in file should be a top-level heading: a leading `@tag` line
+  // (e.g. `@env:test`) legitimately precedes "# Feature: ...".
+  "MD041": false,
+
+  // Headings should be surrounded by blank lines: Tags must be directly in
+  // line before heading
+  "MD022": false,
+
+  // No trailing punctuation in heading: every Gherkin keyword heading ends
+  // in ":" ("# Feature: ...", "## Rule: ...", "### Scenario: ...").
+  "MD026": false
+}