Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

GitHub issues as separate repo?

Tags:

github

There's already an API for GitHub issues, but has anyone succeeded in making it two-way? That is:

git clone [email protected]:user/repo.issues.git # Like for wiki
editor repo.issues/1.json
git push -u origin master

And voilà, a new/updated issue #1!

It could use a pre-receive hook to validate before accepting any pushes, so invalid formatting shouldn't be a problem.

In other words, is there some way to handle the issues of a GitHub project as another GitHub repo?

like image 213
l0b0 Avatar asked Mar 07 '12 17:03

l0b0


People also ask

How do I link issues in GitHub?

To link related issues in the same repository, you can type # followed by part of the issue title and then clicking the issue that you want to link. To communicate responsibility, you can assign issues. If you find yourself frequently typing the same comment, you can use saved replies.

Can you copy an issue in GitHub?

It is not possible to clone issues of GitHub repositories. An alternative for you to get the issues' data would be to use the GitHub APIs. Check out the documentation here to get issues for a repository. You can get the issues' data using the API, store it in file system and then run your necessary scripts on them.

Can 2 people own a GitHub repository?

The free/Individual version allows for up to three "collaborators". That should be exactly what you're looking for. The team versions, on the other hand, allow for multiple collaborators AND "user management". If you wanted finer control over what collaborators can and cannot do, you'd need a team version.

What are GitHub issues used for?

GitHub Issues is a tracking tool that is integrated with your GitHub repository. Use GitHub Issues to focus on important tasks and keep plans up to date simultaneously. Every agile team needs to organize its work, but no one wants to stop working in order to track work.


1 Answers

Aside from using the API, I don't see how this can be done cleanly.

You could put together a (custom) monstrosity that updates a separate GitHub repo with all the issues in said repo at a predefined interval (using the API), but given the effort involved, this better be worth it to you :)

like image 139
Marvin Pinto Avatar answered Oct 01 '22 06:10

Marvin Pinto