dspinellis / dspinellis/git-issue

Looking for Minimal Example of Syncing GitLab/GitHub Issues

Open
#93 3 comments 1 reaction 0 assignees View on GitHub
Dominant language
Shell
Stars
881
Forks
75
PR merge metrics
No merged PRs in 30d

Description

Hey, I tried running the following:

```
git issue init
git issue import gitlab megabyte-labs%2Fnpm%2Fconfigs release
git issue import gitlab megabyte-labs semantic-release-config
git issue new -s 'Testing'
git issue exportall gitlab megabyte-labs%2Fnpm%2Fconfigs release
```
But, it's giving me an error that looks like this:

```
❯ git issue exportall gitlab megabyte-labs%2Fnpm%2Fconfigs release
Creating issue 5cc260f...
gitlab API communication failure
URL: https://gitlab.com/api/v4/projects/megabyte-labs%2fnpm%2fconfigs%2Frelease/issues
Data: {
"title": "Testing",
"description": ""
}
fatal: ambiguous argument '': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git [...] -- [...]'
Operation aborted
```

Any idea on what is going wrong? I really like this project - thanks for making it. *fingers crossed*

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the command sequence in the issue, especially the GitLab exportall command, and capture the API response and resulting Git error. Trace the export path from that CLI entry point to determine why the project URL or revision is empty. Done means the failure is explained and a minimal working GitLab sync example, or a clearly documented limitation, is provided.

Written by the indexing model from the issue text.

Assessment

Tech stack
git, shell
Domain
api, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.