bridge.pipelines.gh2bt_for_meta package#

Public Interface#

This section documents user-facing interface of the bridge.pipelines.gh2bt_for_meta package (as defined in its __init__.py file).

Functions#

run(args)

Run the pipeline to extract bio.tools metadata from a GitHub repository.

Classes#

GitHubToBiotoolsForMetaPipelineArgs(**data)

Pipeline argument model for the GitHub to bio.tools for metadata pipeline.

Pipeline package for extracting (or updating) bio.tools metadata from a GitHub repository.

class bridge.pipelines.gh2bt_for_meta.GitHubToBiotoolsForMetaPipelineArgs(**data)[source]#

Bases: PipelineArgs

Pipeline argument model for the GitHub to bio.tools for metadata pipeline.

Parameters:
  • repo_model (GitHubRepoModel) – The source GitHub repository model.

  • repo_path (str) – The local path to the cloned GitHub repository.

  • existing_metadata (BiotoolsToolModel | None) – Existing bio.tools metadata model, if available. Default is None.

existing_metadata: ToolModel | None#
repo_model: GitHubRepoModel#
repo_path: str#
async bridge.pipelines.gh2bt_for_meta.run(args)[source]#

Run the pipeline to extract bio.tools metadata from a GitHub repository.

Parameters:

args (GitHubToBiotoolsForMetaPipelineArgs) – The pipeline arguments containing the GitHub repository model and existing bio.tools metadata.

Returns:

The extracted or updated bio.tools metadata model.

Return type:

BiotoolsToolModel

Subpackages#

map_funcs

Individual mapping functions for GitHub to bio.tools.

Submodules#

main

Implements the GitHub→bio.tools metadata pipeline: derives a BiotoolsToolModel from a GitHubRepoModel.

map

Mapping classes for GitHub to bio.tools.

Dependencies diagram#

Each architecture diagram below visualizes the internal dependency structure of the bridge.pipelines.gh2bt_for_meta package. It shows how modules and subpackages within the package depend on each other, based on direct Python imports.

  • Packages are shown as purple rectangles

  • Modules are shown as pink rectangles

  • Arrows (A → B) indicate that A directly imports B

Each subpackage’s diagram focuses only on its own internal structure, it does not include imports to or from higher-level packages (those appear in the parent package’s diagram).

bridge package dependencies