Missing Github Repositories from developer tab

@twebermartins is reporting that repos listed in the GitHub field are not showing under the developer tabs: eclipsefdn/emo-team/emo#143 (comment 1010990)

See https://projects.eclipse.org/projects/dt.aas4j/developer

I took a look at the form and the data seems to be entered correctly.

I am thinking this might be a regression from fixing #103 (closed)

Interesting enough, some projects are showing the GH repositories such as: https://projects.eclipse.org/projects/technology.dash/developer

I am wondering if there is a bug in the code where the GH repos are only showing if they also use GL.

mentioned in issue eclipsefdn/emo-team/emo#143 (closed)

assigned to @epoirier

changed the description

added Bug priorityhigh severitymajor team:webdev labels

added statetodo label

FALSE alarm, @mdelgado624 was able to fix the issue..! Thanks!

Hey @cguindon I'm reopening since I did solve the issue but maybe this could be an opportunity to improve the source code repository entry. I do have to fix similar issues regularly, because when committers list their repositories under GitHub or GitLab repos they are not properly shown in the PMI. I usually need to list them twice, both under Source repositories and GitLab/GitHub repositories. Is there a way to improve this behaviour? either by removing the specific GitHub/GitLab listing or by delivering a check message when needed information is missing?

I took the liberty to change the priority and severity of the issue to low, since this is something I can easily fix while we decide if there is something worth doing here.

@mdelgado624 I am definitely open to making some improvements but let's create a separate issue about it!

It's going to be confusing if we use this issue for another reason.

I believe there is a good reason for separating these 2 fields but I totally agree with you that we should revisit/investigate if that can be improved!

I think part of the reason is that our GitLab/GitHub repositories fields are only editable by admin such emo/webmaster versus the source repositories is managed by project members.

If this is a recurrent problem, I think the solution here might be to hide the "admin" fields from project members to avoid confusion or we need to update the field description text to remind projects that they need to update the source repositories field to update the list on developer tab.

If you agree, please open an issue asking us to do one or the other. Otherwise, new issues to revisit this implementation can also work.

Here is the new ticket: #113 (closed)

closed

reopened

added prioritylow label and removed priorityhigh label

added severitylow label and removed severitymajor label

closed