What is language analytics?
Language analytics helps leaders align their organization’s skill development with their software development initiatives. It summarizes the top languages in your organization by course view time. Once a git repository is connected (cloud versions of GitHub, Bitbucket, and Gitlab are currently supported), leaders can compare course view time by language to actual code commits made over the last 31 days.
How do I use language analytics?
Plan administrators and team managers can connect to the git repositories through the language analytics experience located on their dashboard. If a plan administrator or team manager no longer wants to use language analytics for a repository, they can disconnect the git repository. The ability to connect and disconnect a repository is available to all plan administrators and team managers.
How do I connect a repository?
To connect to repository, navigate to the Language Analytics experience on your dashboard.
- Click the Connect a Git repo button.
- Accept the terms and conditions and log in to your git account.
- A dialog box will appear, displaying your repos. Select the repository you want to connect and click the orange Get Started button.
It may take some time for your repository's metrics to load. The larger the repository, the more time it will take to load and may take hours. You can track the progress while it loads in Language Analytics.
Once your repository loads, you can view Language analytics and Pluralsight metrics in the Language Analytics dashboard experience.
How does Pluralsight access a repository?
On the Connect a repository screen, you will enter your repository credentials or access token to GitHub, GitLab, or BitBucket. Then, Pluralsight will pull a list of your repositories you have access to.
When you select a repository to connect to, we pull a one-time snapshot that looks at the commit dates, diff stats, and file extensions from the last 31 days of commits.
We do not pull or store any actual code from your repository.
What data is stored, and how is it secured?
Pluralsight encrypts and stores access credentials to the git vendor you connect to. For Github, this could be a username & password or access token. For GitLab, the only option is to use an access token. For BitBucket, the only option is to use a username & password. These credentials are encrypted at the application level using AES 256. Additionally, the database is encrypted at rest. The credential data is sent to the respective vendor using HTTPS with the strongest level of TLS available from the git vendor.
The only commit data that is stored is a table with the different languages present in commits from the past 31 days and the number of commits made for each language (by looking at diff stats and file extensions). No actual code is stored.
How long is the data stored?
Access credentials and the one-time snapshot will be securely stored in the database until a plan administrator or team manager disconnects the repository from the language analytics dashboard; or until the group plan expires.
What is not stored?
The list of repositories and the actual contents of the code commits are not stored.
Note: Although the data is still stored, the language analytics visualization will not display commits older than 31 days.
If you need help, please email firstname.lastname@example.org for 24/7 assistance.