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
My hypothesis is that these builds are being staged with the number of the last PR to trigger a Plogon commit, which is not necessarily the same as each of the PRs that would be rolled into that commit - which would explain why the earlier update has the authorship of the later update.
The text was updated successfully, but these errors were encountered:
This notification, corresponding to a plugin update by wompscode (#5294), was instead attributed to Populo, who submitted their own update (#5297) which was correctly attributed.
Looking at the code for XLWebServices, it appears that the author information is drawn from the PR number specified in the staged builds:
https://github.com/goatcorp/XLWebServices/blob/1f198735c47b361d477943a1a5c28e2526bc396a/XLWebServices/Controllers/PlogonController.cs#L244
https://github.com/goatcorp/XLWebServices/blob/1f198735c47b361d477943a1a5c28e2526bc396a/XLWebServices/Controllers/PlogonController.cs#L290
And that PR number appears to come from Plogon:
Plogon/Plogon/Program.cs
Line 437 in 9f1619a
My hypothesis is that these builds are being staged with the number of the last PR to trigger a Plogon commit, which is not necessarily the same as each of the PRs that would be rolled into that commit - which would explain why the earlier update has the authorship of the later update.
The text was updated successfully, but these errors were encountered: