mepo

Tool to manage (m)ultiple git r(epo)sitories

https://github.com/geos-esm/mepo

Science Score: 36.0%

This score indicates how likely this project is to be science-related based on various indicators:

  • CITATION.cff file
  • codemeta.json file
    Found codemeta.json file
  • .zenodo.json file
    Found .zenodo.json file
  • DOI references
  • Academic publication links
    Links to: zenodo.org
  • Academic email domains
  • Institutional organization owner
  • JOSS paper metadata
  • Scientific vocabulary similarity
    Low similarity (13.3%) to scientific vocabulary

Keywords

git python repository-management
Last synced: 7 months ago · JSON representation

Repository

Tool to manage (m)ultiple git r(epo)sitories

Basic Info
  • Host: GitHub
  • Owner: GEOS-ESM
  • License: apache-2.0
  • Language: Python
  • Default Branch: main
  • Size: 670 KB
Statistics
  • Stars: 5
  • Watchers: 19
  • Forks: 2
  • Open Issues: 32
  • Releases: 79
Topics
git python repository-management
Created over 6 years ago · Last pushed 10 months ago
Metadata Files
Readme Changelog Contributing License Code of conduct Codeowners Zenodo

README.md

mepo Actions Status DOI Rye Ask DeepWiki

mepo is a tool, written in Python3, to manage (m)ultiple git r(epo)sitories, by attempting to create an illusion of a 'single repository' for multi-repository projects. Please see the Wiki for examples of mepo workflows.

Installation

Using pip

To install mepo using pip, run the following command:

pip install mepo

Using uv

uv install

You can install mepo using the uv package manager. To do so, run the following command:

uv install mepo

uvx

If you'd like to run mepo without installing it, you can use uvx to run it directly:

uvx mepo

Homebrew

Using Homebrew, you can install mepo by installing from the gmao-si-team tap:

brew install gmao-si-team/packages/mepo

This is equivalent to running:

brew tap gmao-si-team/packages brew install mepo

Spack

Mepo is also available via spack as a package. To install mepo using spack, run the following command:

spack install mepo

Transitioning from mepo v1.x to v2.x

If you try to use mepo v2.x within a mepo v1.x repository, you will get an warning message: Detected mepo1 style state Run <mepo update-state> to permanently convert to mepo2 style

To update your repository to work with mepo v2.x, you can run the following command: mepo update-state and it will convert the repository from mepo v1 pickle-state to mepo v2 json-state.

Commands

For more about the possible mepo commands, please see the Mepo Commands wiki page.

Presentation

The SI Team has made a PowerPoint about mepo that can be found here.

Contributing

Please check out our contributing guidelines.

License

All files are currently licensed under the Apache-2.0 license, see LICENSE.

Previously, the code was licensed under the NASA Open Source Agreement, Version 1.3.

Owner

  • Name: Goddard Earth Observing System - Earth System Modeling
  • Login: GEOS-ESM
  • Kind: organization

GitHub Events

Total
  • Create event: 28
  • Release event: 5
  • Issues event: 21
  • Watch event: 1
  • Delete event: 22
  • Issue comment event: 13
  • Member event: 1
  • Push event: 66
  • Pull request review comment event: 2
  • Gollum event: 7
  • Pull request review event: 21
  • Pull request event: 42
Last Year
  • Create event: 28
  • Release event: 5
  • Issues event: 21
  • Watch event: 1
  • Delete event: 22
  • Issue comment event: 13
  • Member event: 1
  • Push event: 66
  • Pull request review comment event: 2
  • Gollum event: 7
  • Pull request review event: 21
  • Pull request event: 42

Issues and Pull Requests

Last synced: 7 months ago

All Time
  • Total issues: 48
  • Total pull requests: 106
  • Average time to close issues: about 2 months
  • Average time to close pull requests: 18 days
  • Total issue authors: 4
  • Total pull request authors: 2
  • Average comments per issue: 0.54
  • Average comments per pull request: 0.24
  • Merged pull requests: 90
  • Bot issues: 0
  • Bot pull requests: 0
Past Year
  • Issues: 14
  • Pull requests: 40
  • Average time to close issues: 3 months
  • Average time to close pull requests: 5 days
  • Issue authors: 2
  • Pull request authors: 2
  • Average comments per issue: 0.36
  • Average comments per pull request: 0.23
  • Merged pull requests: 28
  • Bot issues: 0
  • Bot pull requests: 0
Top Authors
Issue Authors
  • mathomp4 (38)
  • pchakraborty (26)
  • tclune (4)
  • amdasilva (2)
  • WilliamJamieson (1)
Pull Request Authors
  • mathomp4 (91)
  • pchakraborty (55)
Top Labels
Issue Labels
enhancement (22) bug (7) question (4) good first issue (1) documentation (1)
Pull Request Labels
enhancement (35) Skip Changelog (18) bugfix (18) documentation (11) gitflow (8) bug (2)

Packages

  • Total packages: 1
  • Total downloads: unknown
  • Total dependent packages: 0
  • Total dependent repositories: 0
  • Total versions: 10
  • Total maintainers: 2
spack.io: mepo

Tool to manage (m)ultiple git r(epo)sitories

  • Versions: 10
  • Dependent Packages: 0
  • Dependent Repositories: 0
Rankings
Dependent repos count: 0.0%
Average: 29.7%
Forks count: 29.7%
Stargazers count: 30.9%
Dependent packages count: 58.2%
Maintainers (2)
Last synced: 8 months ago

Dependencies

.github/workflows/changelog-enforcer.yml actions
  • dangoslen/changelog-enforcer v3 composite
.github/workflows/run-formatter.yaml actions
  • actions/checkout v4 composite
  • actions/setup-python v5 composite
.github/workflows/run-linter.yaml actions
  • actions/checkout v4 composite
  • actions/setup-python v5 composite
.github/workflows/run-tests.yaml actions
  • actions/checkout v4 composite
  • actions/setup-python v5 composite
pyproject.toml pypi
  • colorama >=0.4.6
  • pyyaml >=6.0.1