Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to specific different develop branch #30

Open
mathomp4 opened this issue Feb 12, 2020 · 1 comment
Open

Add ability to specific different develop branch #30

mathomp4 opened this issue Feb 12, 2020 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@mathomp4
Copy link
Member

Right now mepo develop will only use what's in the components.yaml. But, we should be able to have, say mepo init --develop=dev/gocart and have mepo know internally that develop is now dev/gocart say, and not develop.

Also, have different ways to specify this:

  1. mepo init --develop
  2. With an rc file
    1. Look for $MEPORC in environment
    2. Default to using ~/.meporc

Next question is how to do this and "override" the develop: in the components.yaml

@mathomp4 mathomp4 added the enhancement New feature or request label Feb 12, 2020
@mathomp4 mathomp4 self-assigned this Feb 12, 2020
@tclune
Copy link
Contributor

tclune commented Feb 13, 2020

Probably need to develop slightly different terminology here. We probably still need the notion of "true" develop when those team branches go to the next step to merge. I think calling them a team branch or a community branch would suffice.

mathomp4 added a commit that referenced this issue Feb 14, 2020
This should allow someone to do:
```
mepo init --develop=foo
```
and have the develop branch of *all* repos be `foo`.

It also supports a file `~/.meporc` or the use of `$MEPORC` to point to
a configuration file with:
```
develop: foo
```
mathomp4 added a commit that referenced this issue Oct 29, 2020
…m:GEOS-ESM/mepo into feature/mathomp4/#30-add-develop-override
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants