You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It was observed that sending a Project Viewed Event for commits inherited from the parent project while forking is in most cases (if not all) not a good idea. The reason is that they get accounted for on behalf of the author of the commits (the parent project committer) and as a result, it will cause the fork project to be listed as a recently viewed project for the author. In the general case, this is not true as the author could not even know someone forked his project and for sure it might be the project he recently viewed.
Acceptance criteria:
Perhaps, we should check the push event author and skip sending an event if the push event author is not a member of the project;
It's also worth checking if GL can even provide us with a push event for the commits inherited from the parent project. If not, we should simply skip sending the event in case there's no push event for a commit.
The text was updated successfully, but these errors were encountered:
It was observed that sending a Project Viewed Event for commits inherited from the parent project while forking is in most cases (if not all) not a good idea. The reason is that they get accounted for on behalf of the author of the commits (the parent project committer) and as a result, it will cause the fork project to be listed as a recently viewed project for the author. In the general case, this is not true as the author could not even know someone forked his project and for sure it might be the project he recently viewed.
Acceptance criteria:
The text was updated successfully, but these errors were encountered: