1,720,979 research outputs found
GEOS-ESM/mepo: Fix for using config with "all-in-one" clone
No full textThis fixes a bug in doing:
mepo clone --config UR
GEOS-ESM/mepo: Add per-repo diff
No full textThis release adds a per-repo diff capability a la:
$ mepo diff
Before it was only all repos
GEOS-ESM/mepo: Bug fix for CI Systems
No full textSome CI systems clone repos in odd ways (for GitHub Actions, it's not even a clone!). So, some fixes are needed for the weird edge cases of repository "getting"
GEOS-ESM/mepo: Bug fixes and enhancements for mepo save
No full textThe mepo save command had some issues exposed in recent testing.
The command would save the new yaml file in pwd rather than at the "root" directory where the original was. This was a bit confusing, so the command now saves at root level
mepo save did not handle hashes well. There is no reason it couldn't save to a hash, but it labeled it as a branch in the yaml file which, while not broken, was in consistent
GEOS-ESM/mepo: Obey config file for no style
No full textThis is a bugfix release. Previously, if no style was passed into mepo, by default it chose prefix. This is fine for GEOSgcm, etc. but broke MAPL which uses naked.
For now, if no style is found passed in on the command line or in .mepoconfig assume what is in components.yaml is the correct sytle.
(Updates will be needed to fixtures to support all styles.
GEOS-ESM/mepo: Add mepo reset command
No full textThis release adds a new mepo reset command:
❯ mepo reset -h
usage: mepo reset [-h] [-f] [--reclone] [-n]
Reset the current mepo clone to the original state.This will delete all subrepos and does not check for uncommitted changes! Must be run in the root of
the mepo clone.
options:
-h, --help show this help message and exit
-f, --force Force action.
--reclone Reclone repos after reset.
-n, --dry-run Dry-run only
By default, it will not re-clone a repo and will require a user to answer another question to run (without force flag):
❯ mepo clone
Initializing mepo using components.yaml
ESMA_env | (t) v4.8.0
ESMA_cmake | (t) v3.21.0
ecbuild | (t) geos/v1.3.0
❯ mepo reset
Are you sure you want to reset the project? If so, type 'yes' and press enter. yes
Removing ESMA_cmake/ecbuild...done.
Removing ESMA_cmake...done.
Removing ESMA_env...done.
Removing .mepo...done.
❯ ls -1 ESMA_env | head -1
ls: ESMA_env: No such file or directory
You can do a reclone with --reclone:
❯ mepo clone
Initializing mepo using components.yaml
ESMA_env | (t) v4.8.0
ESMA_cmake | (t) v3.21.0
ecbuild | (t) geos/v1.3.0
❯ mepo reset --reclone -f
Removing ESMA_cmake/ecbuild...done.
Removing ESMA_cmake...done.
Removing ESMA_env...done.
Removing .mepo...done.
Re-cloning all subrepos
Initializing mepo using components.yaml
ESMA_env | (t) v4.8.0
ESMA_cmake | (t) v3.21.0
ecbuild | (t) geos/v1.3.0
Recloning done.
❯ ls -1 ESMA_env | head -1
BASEDIR.rc.in
Note we also require the user to be in the root of a fixture:
❯ mepo clone
Initializing mepo using components.yaml
ESMA_env | (t) v4.8.0
ESMA_cmake | (t) v3.21.0
ecbuild | (t) geos/v1.3.0
❯ cd ESMA_cmake/ecbuild
❯ mepo reset
Error! As a safety precaution, you must be in the root directory of the project to reset
What's Changed
Gitflow. Main to develop by @mathomp4 in https://github.com/GEOS-ESM/mepo/pull/243
Add new reset command by @mathomp4 in https://github.com/GEOS-ESM/mepo/pull/245
Update GitHub Actions by @mathomp4 in https://github.com/GEOS-ESM/mepo/pull/247
GitFlow: Merge Develop into Main For Release by @mathomp4 in https://github.com/GEOS-ESM/mepo/pull/246
Full Changelog: https://github.com/GEOS-ESM/mepo/compare/v1.47.0...v1.48.
GEOS-ESM/mepo: Clean up of mepo save
No full textThis release adds nicety to mepo save where it will add blank lines between the sections in the components-new.yaml file
GEOS-ESM/mepo: Make pull commands more verbose
No full textThis release of mepo makes the mepo pull and mepo pull-all commands verbose by default. Now you will get:
❯ mepo pull ESMA_env
Pulling branch test-branch in ESMA_env
Updating 3ec540d..653348b
Fast-forward
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
X11 forwarding request failed on channel 0
From github.com:GEOS-ESM/ESMA_env
3ec540d..653348b test-branch -> origin/test-branch
instead of just:
❯ mepo pull ESMA_env
Pulling branch test-branch in ESMA_env
It was found that this was a bit too quiet and gave no indication if anything changed.
The older, quieter behavior can be gotten by adding the new --quiet option to pull and pull-al
GEOS-ESM/mepo: Fixes for mepo clone
No full textThis release fixes a bug in mepo clone.
First, it makes the error a bit more clear when you try to mepo clone in a fixture already cloned (see #224):
cd MAPL
mepo clone [email protected]:GEOS-ESM/MAPL.git
Initializing mepo using components.yaml
ESMA_env | (t) v3.11.0
ESMA_cmake | (t) v3.10.0
ecbuild | (t) geos/v1.2.0
mepo clone
ESMA_env | (t) v3.11.0
ESMA_cmake | (t) v3.10.0
ecbuild | (t) geos/v1.2.0
should be an obvious failure. But, nope, there was a bug in the code such that what you'd get is an entire new set of subrepos in that subdirectory!
Now the failure is caught:
cd MAPL/shared
$ mepo clone
fatal: destination path '/Users/mathomp4/Models/MAPL/ESMA_env' already exists and is not an empty directory.
Error! Repo [ESMA_env] already cloned
What's Changed
Fixes #224. Fix for running mepo clone more than once by @mathomp4 in https://github.com/GEOS-ESM/mepo/pull/225
Merge develop into main for release by @mathomp4 in https://github.com/GEOS-ESM/mepo/pull/226
Full Changelog: https://github.com/GEOS-ESM/mepo/compare/v1.42.0...v1.43.
- …
