🚨 You need to enable Continuous Integration on Greenkeeper branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because it uses your CI build statuses to figure out when to notify you about breaking changes.

Since we didn’t receive a CI status on the greenkeeper/initial branch, it’s possible that you don’t have CI set up yet. We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

If you have already set up a CI for this repository, you might need to check how it’s configured. Make sure it is set to run on all new branches. If you don’t want it to run on absolutely every branch, you can whitelist branches starting with greenkeeper/.

Once you have installed and configured CI on this repository correctly, you’ll need to re-trigger Greenkeeper’s initial pull request. To do this, please click the 'fix repo' button on account.greenkeeper.io.

🚀 Feature Proposal

Feature to sparse clone a repo in .meta projects configuration.

Motivation

Some of repos that need to be cloned into meta repo can be mono repos. In the meta repo it would be nice to be able to do a sparse checkout of such a mono repo into the meta repo.

Example

{
"projects": {
"project1": "https://github.com/myorg/repo1.git/project1",
....

automatically git tag and git origin push [tag] with current version number of meta and child repos

🚀 Feature Proposal

(A clear and concise description of what the feature is.)

Motivation

(Please outline the motivation for the proposal.)

Example

(Please provide an example for how this feature would be used.)

on Unbuntu 17.10. Doesn't seem to like the double quotes (but this works fine for meta git commit -m "commit msg"

Failing:

kbroch@barolo:/home/kbroch/metatest  git:(master) $ node --version
v8.9.4
kbroch@barolo:/home/kbroch/metatest  git:(master) $ meta --version
1.0.48
kbroch@barolo:/home/kbroch/metatest  git:(master) $ meta git tag -a RC -m "release candidate"

metatest:
fatal: Failed to resolve 'candidate' as a valid ref.
metatest exited with error: Error: Command failed: git tag -a RC -m release candidate

test:
fatal: Failed to resolve 'candidate' as a valid ref.
test exited with error: Error: Command failed: git tag -a RC -m release candidate

testlabelcopy:
fatal: Failed to resolve 'candidate' as a valid ref.
testlabelcopy exited with error: Error: Command failed: git tag -a RC -m release candidate

Passing:

kbroch@barolo:/home/kbroch/metatest  git:(master) $ meta git tag -a RC -m release-candidate  

metatest:
metatest ✓

test:
test ✓

testlabelcopy:
testlabelcopy ✓

Would it be possible to add the corresponding path to the output of meta git status for each of the projects in meta. It would make navigating to them much easier to do commits etc.

Current output:

meta-test:
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working tree clean
meta-test ✓

project-test:
On branch master
Your branch is up-to-date with 'origin/master'.

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: go.mod
modified: go.sum
modified: main.go

no changes added to commit (use "git add" and/or "git commit -a")
project-test ✓

New Output:

meta-test:
On branch master
Your branch is up-to-date with 'origin/master'.

nothing to commit, working tree clean
meta-test ✓

project-test (projects/project-test):
On branch master
Your branch is up-to-date with 'origin/master'.

Changes not staged for commit:
(use "git add ..." to update what will be committed)
(use "git checkout -- ..." to discard changes in working directory)
modified: go.mod
modified: go.sum
modified: main.go

no changes added to commit (use "git add" and/or "git commit -a")
project-test ✓

https://github.com/mateodelnorte/find-file-recursively-up

🤓 Question

What's the difference between meta git <command> and meta exec "git <command>", for those operations supported by meta git?

Implement git remote sub-command. I would think at the minimum the following sub-commands would be useful.

• git remote -v
• git remote show origin
• git remote rename oldname newname
• git remote rm name

🚀 Feature Proposal

meta git ls-files [<file>...]

shows files under control version in all meta repositories

Motivation

To have a easy way to see all files that match with a given pattern in the repo and sub repos

P.S.

Thanks for the tool! It is great!

One of the best solution to the "coordination of repos" problem. Better than git submodules and other official approaches

🤓 Question

(You must search the issues before asking your question. Please consider asking in Gitter first.)

Sorry havent used gitter before, couldnt find gitter.im/meta it on their webpage.

Is it possible to have a meta git command run against a subset of the repos defined in the .meta file rather than all of them? For example if I want to create a branch in 3 out of 10 repo's is this possible with the meta git plugin?

Thanks,
Damian.

causes project to be doubly added. not needed.

space/quote detection seems to be broken, or quotes are not being placed around subcommand:

$ meta git commit -m 'bumping to message-bus.7' --include-only Mercury,dataflow,data-ready-svc,kronos,echo,trident
'C:\Program' is not recognized as an internal or external command,
operable program or batch file.

https://stackoverflow.com/questions/1778088/how-to-clone-a-single-branch-in-git
https://stackoverflow.com/questions/4811434/clone-only-one-branch

https://github.com/mateodelnorte/meta-git/blob/master/bin/meta-git-pull#L13 needs to be changed to allow: /.*/.

Hi,

I use the following command to push and set the origin of a branch :

meta git push --set-upstream origin 1.3.x

But I got the following errors in each of my modules :

my_module:
fatal: The current branch 1.3.x has no upstream branch.
To push the current branch and set the remote as upstream, use

    git push --set-upstream origin 1.3.x

my_module exited with error: Error: Command failed: git push 1.3.x --set-upstream origin

It looks like my push command has been transformed by meta in a bad way.

Meta version : 1.0.48

Thx

hi,

sorry for my poor english.

i found meta git clone can't set the self dirname, is it a bug?

Hello!

I've encountered consistent problem, while trying to run typical git pattern. When running meta git pull --rebase {remote} {branch}, git-meta instead runs git pull {branch} --rebase {remote}, which is not a working thing.

Git version 2.17.0
Os: MacOS 10.13 (Darwin 17.7.0 Darwin Kernel Version 17.7.0)

Here's specific example output:

➜  meta git:(feature/xxxx) ✗ meta git pull --rebase origin master

meta:
fatal: 'master' does not appear to be a git repository
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
meta: command 'git pull master --rebase origin' exited with error: Error: Command failed: git pull master --rebase origin

I would like to deal with issue on my own, since it will make my life much easier :)

1. Please confirm it's a bug, or it should be done in some other way.
2. Maybe there are any use cases, when this behaviour is correct, so I do not miss them?
3. Any recommendations on contributing to the code are welcome, but not mandatory :)

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Rate-Limited

These updates are currently rate-limited. Click on a checkbox below to force their creation now.

• chore(deps): update dependency husky to v9
• chore(deps): update dependency prettier to v3
• chore(deps): update dependency pretty-quick to v4
• fix(deps): update dependency commander to v12
• 🔐 Create all rate-limited PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• fix(deps): update dependency debug to v4.3.4
• fix(deps): update dependency get-meta-file to v1.3.6
• fix(deps): update dependency loop to v3.3.6
• fix(deps): update dependency meta-exec to v1.4.4
• fix(deps): update dependency meta-loop to v1.2.5
• chore(deps): update dependency commitizen to v4.3.0
• chore(deps): update dependency prettier to v2.8.8
• chore(deps): update dependency pretty-quick to v3.3.1
• chore(deps): update commitlint monorepo to v19 (major) (@commitlint/cli, @commitlint/config-conventional)
• chore(deps): update dependency jest to v29
• Click on this checkbox to rebase all open PRs at once

Ignored or Blocked

These are blocked by an existing closed PR and will not be recreated unless you click a checkbox below.

• fix(deps): update dependency chalk to v5

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Not a bug report but a notification of a security issue

$ npm audit | grep -B1 -A11 Critical
┌───────────────┬──────────────────────────────────────────────────────────────┐
│ Critical      │ Command Injection                                            │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Package       │ meta-git                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Patched in    │ No patch available                                           │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Dependency of │ meta-git                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path          │ meta-git                                                     │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info     │ https://npmjs.com/advisories/1457                            │
└───────────────┴──────────────────────────────────────────────────────────────┘

$ git log -n1
commit 1b727d56b7f09d3f27788ac02346f184622d36de (HEAD -> master, origin/master, origin/HEAD)
Author: Renovate Bot <[email protected]>
Date:   Tue Jun 8 22:39:39 2021 +0000

    chore(deps): update dependency trim-newlines to 3.0.1 [security]

🚀 Feature Proposal

Run git commands on all available branches using something like --all-branches.

Motivation

Working on a project with many repos, I often find myself working on multiple branches of the same repo when I collaborate with multiple members of my team. It would be nice to have a simple way to see all the local changes I currently have on all those branches in a simple way.

Example

➜  meta-repo git:(master) meta git status --all-branches

/path/to/my/repos/repo1: 
On branch master 
nothing to commit, working tree clean
/path/to/my/repos/repo1: ✓

/path/to/my/repos/repo1: 
On branch feat-1
nothing to commit, working tree clean
/path/to/my/repos/repo1: ✓

...