You can either get us to maintain your personal or business email (creating or removing email addresses, for example), or you can choose to manage it yourself - all accounts come with full cPanel access. Your domain(s), either for your personal or business's email (and, optionally, web sites) can be hosted on our fast, dedicated uk based server. If you need help, please contact Pluralsight Support.Apple-Friendly Email Service The Ultimate Apple-Compatible Email Service * The undisclosed email follows these structures: In both instances, Flow creates an alias and labels the users Undisclosed. Other times, the user’s account and email are set as private. This can happen when a githost or ticket system doesn’t provide the account name or email. Undisclosed users appear in the user list and in reports when a githost doesn’t provide a user’s email address during integration. Sometimes Flow cannot can’t access the account name or email in the API. When Flow integrates a githost or ticket system, it pulls information from an API. When Flow can’t identify a user, that user is Undisclosed. Note: If the user has a login to Flow, be cautious about changing their apex alias so their ability to log in won't be interrupted. Confirm their other related aliases are in the Users queued to merge section.Search for the user and drag the desired apex user into the Select a target user box.In the left navigation under User Management, click Users.An apex alias is the primary alias used to identify a user in your reports. This number includes:įlow assigns an apex alias to each user imported from connected integrations. In this case, Flow creates two additional aliases.Ĭhandler’s total alias count is five. In addition to these aliases, Flow generates a unique alias from each integration it imports data from. Fork Repo B, imported via integration 2įlow ingests this user’s three existing aliases from GitHub.Let's say Chandler commits on the following three repos imported from two different integrations. This is necessary if there are multiple integrations connected to the same Git host. Flow generates these aliases to track whose data came from what integration. An example of a Flow-created alias is aliases are automatically merged under their respective user. In addition to aliases found when first ingesting your data, Flow creates a new alias for each ingested user or contributor. Outside of Flow, Chandler used each alias to either comment on a PR, create a commit, or create a ticket. The User details page has every alias imported from these integrations.įlow pulled two aliases from GitLab. In the example below, Chandler connects the following Integrations into their Flow account: The Aliases tab lists all merged aliases for the user.Ī user has unique aliases imported from each integration set up in Flow. Click the number in the Alias column to view all merged aliases.Ĭlick the user to see the users details page.Locate the user whose aliases you want to view.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |