Skip to content
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

Organisation level #5

Open
andymac4182 opened this issue Feb 20, 2017 · 3 comments
Open

Organisation level #5

andymac4182 opened this issue Feb 20, 2017 · 3 comments

Comments

@andymac4182
Copy link

@andymac4182 andymac4182 commented Feb 20, 2017

It would be great if this could be pointed at a Github Organisation to allow for summarising and working on issues across repos.

@DavidWells
Copy link
Contributor

@DavidWells DavidWells commented Feb 20, 2017

That would be cool. But isn't something we have planned.

The database schema would need to be updated to achieve this. Right now the items store via the issue numbers which are unique per repo but not across multiple repos.

So the dynamo primary keys would need to be like repo_name_1, repo_name_2 etc.

@quantuminformation
Copy link
Contributor

@quantuminformation quantuminformation commented Feb 21, 2017

Am I missing something here, isn't scope part of serverless?

@DavidWells
Copy link
Contributor

@DavidWells DavidWells commented Feb 21, 2017

@quantuminformation scope works for single repos right now.

The question is if it can pull in multiple repos into the columns at once.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.