Stackalytics does not ensure configuration email order during
processing. Thus additional field is required to ensure a proper
email is used to compile gravatar url.
Signed-off-by: Andrii Ostapenko <email@example.com>
Original company names are currently used in activity logs links and
user profile that break the link in case if company name contains '&'
or any other non-safe for url symbol. Thus avoid using original names
in favor of normalized ones.
Signed-off-by: Andrii Ostapenko <firstname.lastname@example.org>
Previously only one gerrit_id for user_profile was supported and took
part in record_processing. In case of using multiple Gerrits or multiple
gerrit_ids in one Gerrit, while merging profiles all except one
gerrit_ids were rejected.
This commit adds new user gerrit_ids user_profile key containing all
required mapping between multiple Gerrits and gerrit_ids. Each gerrit_id
acts the same way as old gerrit_id during review record processing, that
potentially increases success rate of record identification and
decreses amount of unnecessary launchpad user queries by storing user
with all gerrit_ids as a primary key instead of one.
Also changes to UI added to represent multiple Gerrit accounts.
With this commit disagreements will be processed after cores are
determined. This way disagreements will be processed with actual core
list or, even more for initial data population, with existent core list.
In last case disagreements could not be determined at all.
Before this commit merge date was determinde by review lastUpdated
attribute, that could lead to severe inaccuracy in case if review was
updated by any comment after change is merged (e.g. cherry-pick via
gerrit in half a year)
This is a mechanically generated change to replace openstack.org
git:// URLs with https:// equivalents.
This is in aid of a planned future move of the git hosting
infrastructure to a self-hosted instance of gitea (https://gitea.io),
which does not support the git wire protocol at this stage.
This update should result in no functional change.
For more information see the thread at
Also adds an option 'report-default-limit' that allows to configure
default amount of changes to present in open changes report, in case
if limit query parameter is not provided.