I expected add to clone the sub project.
Instead it creates an empty .git repo and sets the remote without setting the upstream of master to origin/master nor does it get the latest from origin/master. This makes adding a project slightly less intuitive.

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

File: .github/renovate.json
Error type: The renovate configuration file contains some invalid settings
Message: Invalid regExp for packageRules[0].packagePatterns: ^meta-,find-file-recursively-up,get-meta-file,loop,symlink-meta-dependencies``

🐛 Bug Report

git remote remove origin throws fatal error if origin doesn't exist and meta create uses it to initialized the child repositories and hence the child repo don't have a remote added to them. The current fix is removing the folders and running meta git update so that everything clones properly

🚨 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

The create command should try to infer the origin remote from a project if it already exists in the local filesystem.

Motivation

I manually moved some repos into a metarepo today, and I would've preferred not to manually track down the git urls to satisfy meta project create.

when calling meta project add ... if the project I'm adding is a meta repo, it should also behave the same as if I'd called meta git clone ....

🤓 Question

Are there any special reason for not importing repositories outside the actual repository?

meta-project-import:32-37

const metaPath = getMetaFile.getFileLocation();
const dest = path.relative(path.dirname(metaPath), path.resolve(destArg));
if (dest[0] === '.') {
    console.error(`💥 Projects cannot be outside the meta repo: ${cyan(dest)}`); // prettier-ignore
    process.exit(1);
}

If your meta folder is named smth. like 'abc.meta' adding a new project will cause this error:

adding abc.pro1 to .gitignore at /home/user/dev/src/abc.gitignore/.meta
/home/user/dev/src/abc.gitignore/.meta does not exists. Creating it now.
fs.js:122
    throw err;
    ^

Error: ENOENT: no such file or directory, open '/home/user/dev/src/abc.gitignore/.meta'
    at Object.openSync (fs.js:448:3)
    at module.exports (/home/user/.npm/lib/node_modules/meta/node_modules/meta-project/lib/addToGitIgnore.js:12:23)
    at find (/home/user/.npm/lib/node_modules/meta/node_modules/meta-project/bin/meta-project-add:66:9)
    at findIn (/home/user/.npm/lib/node_modules/meta/node_modules/find-file-recursively-up/index.js:18:14)
    at module.exports (/home/user/.npm/lib/node_modules/meta/node_modules/find-file-recursively-up/index.js:28:10)
    at exec (/home/user/.npm/lib/node_modules/meta/node_modules/meta-project/bin/meta-project-add:60:7)
    at module.exports (/home/user/.npm/lib/node_modules/meta/node_modules/meta-exec/index.js:56:18)
    at exec (/home/user/.npm/lib/node_modules/meta/node_modules/meta-project/bin/meta-project-add:51:5)
    at module.exports (/home/user/.npm/lib/node_modules/meta/node_modules/meta-exec/index.js:56:18)
    at mkdirp (/home/user/.npm/lib/node_modules/meta/node_modules/meta-project/bin/meta-project-add:44:3)

/home/user/dev/src/abc.meta/.meta -> /home/user/dev/src/abc.gitignore/.meta does not exists

Maybe thats the place to check:
addToGitIgnore(metafilePath.replace('.meta', '.gitignore'), destFolder);

🐛 Bug Report

Incorrect path in .gitignore after meta project create for Windows 10
meta version 2.2.10
meta-project version 2.2.9
git version 2.24.0.windows.2

To Reproduce

1. init git and meta

meta init
git init

2. add project with subfolder (Windows 10)

meta project create packae/project1 [email protected]:project1.git

3. see .gitignore file (added directory looks like /packae\project1/)
4. try to add files to git

git add ./

result:
error: 'packae/project1/' does not have a commit checked out
fatal: adding files failed

Expected behavior

git command should success.

note: If I change path in .gitignore from "/packae\project1/" to "/packae/project1/" git command works correctly.

This plugin appears incomplete, I expected a meta project remove <file-path> to exist, but it either doesn't or it is not documented.

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 pretty-quick to v4
• fix(deps): update dependency commander to v12
• fix(deps): update dependency rimraf to v6
• 🔐 Create all rate-limited PRs at once 🔐

Edited/Blocked

These updates have been manually edited so Renovate will no longer make changes. To discard all commits and start over, click on a checkbox.

• fix(deps): update dependency mkdirp to v0.5.6

Open

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

• 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 husky to v9
• chore(deps): update dependency jest to v29
• chore(deps): update dependency prettier to v3
• fix(deps): update dependency chalk to v5
• fix(deps): update dependency mkdirp to v3
• 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 tildify to v3

Detected dependencies

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

🚀 Feature Proposal

The projects object in .meta should support custom git branches.

Motivation

The master branch isn't always appropriate.

Example

meta project import foo https://github.com/aleclarson/foo.git -b not-master

The .meta config could look like this:

{
  "projects": {
    "foo": {
      "url": "https://github.com/aleclarson/foo.git",
      "branch": "not-master"
    }
  }
}

🐛 Bug Report

When I run the meta project import command, I often forget to add both dest and repoURL params. Instead I just add one param (usually the repo URL). Meta then proceeds to modify the .gitignore file, then tries to clone the repo but fails, hence not modifying the .meta file. The .gitignore file now contains the git URL, which is not correct.

To Reproduce

Example:

> meta project import [email protected]:eddex/some-repo.git
{ repoUrl: undefined, dest: '[email protected]:eddex\\some-repo.git' }

~\work\meta-repo:
fatal: repository 'undefined' does not exist
~\work\meta-repo: command 'git clone  undefined [email protected]:eddex\some-repo.git' exited with error: Error: Command failed: git clone  undefined [email protected]:eddex\some-repo.git
Appending to ~\work\meta-repo\.gitignore
Updating "projects" in ~\work\meta-repo\.meta

✓ Project imported: [email protected]:eddex\some-repo.git

The only modified file after this command is the .gitignore, meta adds the dest param (which in this case is the git URL):

+/[email protected]:eddex\some-repo.git/

Expected behavior

If only one param is detected (one of them is null/undefined), the command should be aborted and no files should be modified.

Alternatively, it would be great to allow only passing the repoURL and automatically parsing the repo name from it.