Welcome to Pluralsight Flow. Before you can explore the features and reports available to you, you must complete your initial configurations. These configurations make sure your data is imported in a way that makes sense for your organization. If you don’t take these steps now, it may take several days to update your data in the future.
Note: If you plan to use Flow with an internal server or behind a firewall, allowlist Flow's static IP addresses so Flow can access your Git repositories.
Before getting started
Now that you have access to Flow, make sure to add anyone else who will be helping to set Flow up.
Admins are responsible for connecting your organization’s integrations and making sure Flow has access to your data. Admins need to understand the workflow of teams and what integrations and repos those teams work on.
Flow automatically chooses an admin when a Flow organization is created. If you're not the right person to manage your organization's configurations and data, select at least one other person to be a Flow admin.
You must have the correct permissions to view Settings home.
To view Settings home, you must have the following permissions:
- View and manage integrations or View, manage, and delete integrations
- Manage group programming
- Manage users & teams
If you are missing any of these permissions, you can’t see Settings home. Learn more about administrative permissions.
Use Settings home to make setting your configurations easier. Settings home walks you through the most important Flow configurations, ensuring you don’t miss anything.
Follow Flow's guided steps for setup. To change configurations later, either return to Settings home or access these same configurations through the side navigation.
To access Settings home, navigate to Flow and click Settings in the top navigation. From there, follow the guide to change configurations or use the side navigation to access other settings.
When starting with Flow, set your configurations according to the steps provided in Settings home. Make sure these configurations match your company practices.
In step 1, set your default domain.
When developers make commits, the username of those commits may vary. Your default domain designates the email domain of the user name that is picked as the main user. If more than one user account is found for a person, Flow uses the default domain to determine the correct account.
Initially, the default domain is based on the first administrator's email address. Check that this default is correct so you can easily merge users after your data is ingested.
Important: If your default domain isn't set correctly when merging users, your Flow data will be inaccurate and you will need to update the default domain and manually merge and unmerge users in the future. This can be a lengthy process. Ensuring your default domain matches the domain you want to use for apex users saves you time in the future. Setting this up before you import data is the fastest path to success.
In step 2, set your Group programming preferences. Group programming is enabled by default.
Visualize contributions made by multiple users with group programming and customize how group work is credited to multiple people. This helps Flow know how to handle co-authored commits.
Disable group programming or further customize it for your needs.
In step 3, set your auto-merge preferences.
Auto-merge is enabled by default. If there are names or emails you don’t want to include in auto-merge, add them in the Exclusions section’s text box, separated by commas.
Auto-merge automatically merges aliases based on the user’s sign in email address or user email addresses. Aliases with the same email addresses merge regardless of their usernames.
Pull in data
Next, add integrations and import repos. Follow the steps in Chapter 2 of the getting started guide.
Now that you've set up your initial configurations, import your data and learn how to manage it.
If you need help, please contact Pluralsight Support.