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

Multiple projects with same name but different provider #1010

Open
v-g-ustinov opened this issue Dec 20, 2016 · 3 comments
Open

Multiple projects with same name but different provider #1010

v-g-ustinov opened this issue Dec 20, 2016 · 3 comments

Comments

@v-g-ustinov
Copy link

We have two projects with same names on bitbucket and github. It is different projects but have the same names and same names for repositories.
Bitbucket's one is already configured and now I get "error:409 project already exists" if I try to add the repo with same name from github. As project names and repos are not global and really can have the same names it should be prefixed some how locally or fixed other way.

@xgalen
Copy link
Member

xgalen commented Dec 29, 2016

Hi @v-g-ustinov ,

As you pointed, strider only matches the name field:

Project.findOne({name: name}, projectResult);

The name is composed by the organization / repo's name, so we can suppose that your organization has the same name also.

The easy patch could be change the previous line by something like (just add a new filter by provider.id):
Project.findOne({name: name, provider.id: provider.id}, projectResult);

But I don't know if this can has unexpected consequences. Maybe you can change the line, try it and if it works, do make a PR.

Alfredo

@knownasilya
Copy link
Member

It would cause issues, because the provider isn't reflected in the url so strider wouldn't know which project you mean..

@knownasilya
Copy link
Member

This would actually be an easy implementation detail most likely.

@knownasilya knownasilya changed the title Error creating project Multiple projects with same name but different provider Dec 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants