-
Notifications
You must be signed in to change notification settings - Fork 2
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
Labels
enhancement
New feature or request
Comments
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
Mar 3, 2020
mathomp4
added a commit
that referenced
this issue
Jun 10, 2020
mathomp4
added a commit
that referenced
this issue
Jun 15, 2020
mathomp4
added a commit
that referenced
this issue
Sep 18, 2020
mathomp4
added a commit
that referenced
this issue
Oct 7, 2020
mathomp4
added a commit
that referenced
this issue
Oct 28, 2020
mathomp4
added a commit
that referenced
this issue
Oct 29, 2020
mathomp4
added a commit
that referenced
this issue
Oct 29, 2020
…m:GEOS-ESM/mepo into feature/mathomp4/#30-add-develop-override
mathomp4
added a commit
that referenced
this issue
Oct 30, 2020
mathomp4
added a commit
that referenced
this issue
Nov 20, 2020
tclune
added a commit
that referenced
this issue
Mar 8, 2021
mathomp4
added a commit
that referenced
this issue
May 19, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now
mepo develop
will only use what's in thecomponents.yaml
. But, we should be able to have, saymepo init --develop=dev/gocart
and havemepo
know internally that develop is nowdev/gocart
say, and notdevelop
.Also, have different ways to specify this:
mepo init --develop
$MEPORC
in environment~/.meporc
Next question is how to do this and "override" the
develop:
in thecomponents.yaml
The text was updated successfully, but these errors were encountered: