Skip to content

Show last push widget in upstream after push to fork

What does this MR do?

Show the last push widget in the upstream project when you push to a fork.

Are there points in the code the reviewer needs to double check?

In the view, I'm checking if @project in the first part of the conditional. I felt it was necessary in case @project wasn't an object in all cases. Will it ever not be there? Is this check necessary?

Should there be tests? I don't see existing ones for this.

Why was this MR needed?

I use the fork workflow everywhere and it has annoyed me for some time that the last push widget doesn't show up when viewing the upstream project. I'm almost never viewing the fork in GitLab so I want to be able to easily create a MR in any case.

Screenshots (if relevant)

Widget in upstream repo:

Screen_Shot_2016-06-23_at_10.05.29_AM

Widget in fork:

Screen_Shot_2016-06-23_at_10.05.25_AM

Widget on dashboard:

Screen_Shot_2016-06-23_at_10.06.07_AM

Merge request reports