Review messages and readme

README.md

@@ -9,7 +9,7 @@
 | [Features and Configuration](#features-and-configuration)
 | [Advanced Features](#advanced-features)
 | [Combined Dependabot Updates](#combined-dependabot-updates)
-| [Follow Up](#follow-up)
+| [Follow-up](#follow-up)
 | [Contributing](contributing)
 
 ## Overview
@@ -51,42 +51,42 @@ A provider is defined by a repository type (GitHub, GitLab), an *user* and an ac
 You can define any combination (e.g. providers with the same username but different token, or different username but same token).
 
 ### Api acces token encryption
-As mentioned before, the configuration is stored in the browser local memory and all processing occours in the browser.
+As mentioned above, the configuration is stored in the browser local memory and all processing occours in the browser.
 To protect sensistive information (the access tokens) the user is given the option to encrypt the tokens using a password.
 If you set a password, the next time that you open DashGit you will be asked for the password.
 
-If you forgot the password, you are given with the option of skip. In that case you may notice that api calls fail, you should go
-to the configuration to reset the tokens to an empty value.
+If you forgot the password, you are given with the option of skip. In that case you may notice that api calls fail: you should go
+to the configuration to reset the tokens.
 Note that once a token is encrypted, you can't decrypt it, only reset.
 
 ### Selecting, sorting and grouping
 The user can customize how the work items are sorted and organized by setting the controls that appear at the top of the header.
-This settings are no stored in the configuration.
+These settings are no stored in the configuration.
 
 ### Scope configuration
-The username is the reference user for which the work items are displayed (assigned to, created by, etc.)
+The *username* is the reference user for which the work items are displayed (assigned to, created by, etc.)
 and the token defines the scope of the request that determines what items are displayed.
-Note that the username can be someone other the token owner.
+Note that the username can be someone other than the token owner.
 
 - The scope of Assigned, Involved and Created views is whatever repository visible for the token.
 - The scope of Unassigned and Dependabot views is restricted to the repository of the token owner. 
-  If you need include other users or organizations, you must include them in the `Add owners to unassigned`
+  If you need to include other users or organizations, you must set them in the `Add owners to unassigned`
   or `Add owners to dependabot` parameters, respectively.
-- The scope of Branches view is handled differently, as data is obtained by the GraphQL API requests insetead of the REST API.
-  On GitHub you will specify one or more than the following scopes: OWNER, ORGANIZATION_MEMBER or COLLABORATOR.
+- The scope of Branches view is handled differently, as data is obtained by the GraphQL API requests instead of the REST API.
+  On GitHub you have to specify one or more than the following scopes: OWNER, ORGANIZATION_MEMBER or COLLABORATOR.
 
-### Filtering
+### Filtering configuration
 The requests made against the repositories get the most recent work items that fit on a single response page,
 that is enough for the most common use case to display the open work items regarding the user.
-Moreover the data displayed can be restricted by setting any of the following parameters:
+Moreover, the data displayed can be restricted by setting any of the following parameters:
 - `Max age`: Filters out the work items that are older than the days specified.
 - `Filter if Label`: Filters out the work items that contain the label specified.
 
-### Status cache
+### Status cache configuration
 Requests to the GraphQL API to get the branches and build statuses are expensive if they retrieve data
 from many repositories and are subject to more restrictive rate limits than REST API.
 To mitigate potential problems with API rate limits and improve the UI response times, these calls are cached and managed
-by two parameters (measured in seconds):
+by two parameters (measured in seconds) that you can tune in the Configuration tab:
 - `Status Cache Update Time`: During this period, any call to get statuses returns the cached data.
   This is to avoid making API calls when the user moves from a view to another in a short period of time.
   When this period of time expires, the cache will be incrementally updated by requesting 
@@ -104,16 +104,16 @@ As DashGit works entirely in the browser without a backend server, before using
 you have to set up a dedicated (private) repository 
 that we call *manager repository*: 
 - Create the manager repository in GitHub: It is recommended to keep private, since although no token is sent to it, 
-  the logs may contain sensitive information such as urls or usernames when using private or on-premises repositories.
+  the logs may contain sensitive information such as urls or usernames when accesing to private or on-premises repositories.
 - Enable the manager repository: Go to the Configure tab and check the *Enable a Manager Repository for advanced functions*.
   Provide the name of the manager repository (REPO/OWNER) and the token used to push the combined updates or follow-up payload.
 
 ### Combined Dependabot Updates
 
 From the Dependabot tab you can combine pull requests with dependency updates generated by dependabot
-into a sigle PR per repository and merge them automatically with just a few clicks. 
+into a sigle PR per repository and merge all of them automatically with just a few clicks. 
 
-After you confirm the updates to be combined, DashGit pushes a json file with this information to the manager repository
+After you select and confirm the updates to be combined, DashGit pushes a json file with this information to the manager repository
 (*update payload*).
 Then, the manager repository runs a GitHub Actions workflow to create each combined pull request, resolve merge conflicts
 with adjacent lines and enable automerge.
@@ -126,14 +126,14 @@ This requires the previous setup of the manager repository (see above) and a lit
   Create these tokens in the manager repository. Their stored value has to be a token used to create the combined PRs.
 
 Notes:
-- On GitLab the projects have automerge enabled by default, but on GitHub you need to explicitly enable per repository
+- On GitLab, the projects have automerge enabled by default, but on GitHub you need to explicitly enable per repository
   from Settints->General. It is recommended to activate the automatic deletion of head branches when PRs are merged.
-- On GitHub, to automerge when the build succeeds you have to configure the repository to require status checks to pass before merging
-  (to do so, create an branch protection rule on the main branch, check this option and specify the checks that must pass)
+- On GitHub, to automerge when the build succeeds you have to configure the repository to require status checks to pass before merging.
+  To do this, create an branch protection rule on the main branch, check this option and specify the checks that must pass.
 - On GitLab, you can generate dependabot updates using the [Dependabot Script](https://github.com/dependabot/dependabot-script)
   or using [this more customized version of Dependabot Script](https://github.com/javiertuya/dependabot-script).
 
-### Follow up
+### Follow-up
 
 The *Follow up* view displays all work items that you have flagged for follow up.
 You can flag any work item from any view by clicking the left icon(s) and entering 

dashgit-web/app/ConfigView.js

@@ -46,14 +46,22 @@ const configView = {
     return `
     <div class="card mt-2 text-bg-light" id="config-providers-common">
       <div class="card-body pt-2 pb-2">
+        ${data.providers.length == 0
+        ? `<p class="card-text mb-1 text-danger">To start using DashGit you have to sdd a GitHub or GitLab provider and set the username that is accessing the repository. `
+          + `This will give you access to the public repositories at github.com or gitlab.com.</p>`
+          + `<p class="card-text mb-1 text-danger">It is recommended to configure an API Access Token because unauthenticated providers are subject to lower rate limits and do not allow you to view branches, build statuses and notifications.</p>`
+        : ""}
+
         <p class="card-text mb-1">
           ${data.encrypted
         ? "API access tokens in this configuration will be saved encrypted. If you forget your password you will have to reset both password and tokens."
         : "This configuration is stored in the browser local memory. You can set up a password to encrypt the API access tokens."
-      }
+        }
         </p>
+
         ${this.anyGitHubWithoutToken(data)
-        ? `<p class="card-text mb-1 text-danger">GitHub unauthenticated providers are subject to lower rate limits and do not allow you to view branches, build statuses and notifications.</p>`
+        ? `<p class="card-text mb-1 text-danger">GitHub unauthenticated providers are subject to lower rate limits and do not allow you to view branches, build statuses and notifications. `
+          + `It is recommended to set an API Access Token.</p>`
         : ""}
 
         <h6 class="card-subtitle mb-1 mt-1 text-body-secondary">Common parameters:</h6>
@@ -113,7 +121,7 @@ const configView = {
             "The default scope of Unassigned view is restricted to the repository of the token owner. Here you can include other users or organizations (separated by spaces)")}
           ${this.array2html(`config-providers-dependabotAdditionalOwner-${key}`, "text", "Add owners to dependabot", provider.dependabotAdditionalOwner, '', "225", "150",
             "The default scope of Dependabot view is restricted to the repository of the token owner. Here you can include other users or organizations (separated by spaces)")}
-          ${this.check2html(`config-providers-enableNotifications-${key}`, "Show notifications", provider.enableNotifications)}
+          ${this.check2html(`config-providers-enableNotifications-${key}`, "Show notifications/mentions", provider.enableNotifications)}
         </div>
 
         <div class="row">
@@ -122,15 +130,15 @@ const configView = {
         </div>
         <div class="row config-providers-graphql-settings">
           ${this.input2html(`config-graphql-maxProjects-${key}`, "number", "Max projects", provider.graphql.maxProjects, 'required min="2" max="100"', "150", "100",
-            "Maximum number of repositories/projects that are retrieved to get the branches and statuses")}
+            "Maximum number of repositories/projects that are retrieved to get the branches and build statuses")}
           ${this.input2html(`config-graphql-maxBranches-${key}`, "number", "Max branches", provider.graphql.maxBranches, 'required min="2" max="100"', "150", "100",
             "Maximum number of branches that are retrieved for each repository/project to get the build statuses")}
           ${provider.provider == "GitLab"
             ? this.input2html(`config-graphql-maxPipelines-${key}`, "number", "Max pipelines", provider.graphql.maxPipelines, 'required min="2" max="100"', "150", "100",
-              "Maximum number of pipeline runs that are retrieved for each repository/project to get the branches and statuses")
+              "Maximum number of pipeline runs that are retrieved for each repository/project to get the branches and build statuses")
             : this.check2html(`config-graphql-include-forks-${key}`, "Include Forks", provider.graphql.includeForks)
               + this.check2html(`config-graphql-only-forks-${key}`, "Only Forks", provider.graphql.onlyForks)
-              + (this.raw2html(" - API scope:", "Specifies the scope of the GitHub GraphQL API requests that get the branches and statuses") + " &nbsp; "
+              + (this.raw2html(" - API scope:", "Specifies the scope of the GitHub GraphQL API requests that get the branches and build statuses") + " &nbsp; "
               + this.check2html(`config-graphql-scope-owner-${key}`, "Owner", provider.graphql.ownerAffiliations.includes("OWNER"))
               + this.check2html(`config-graphql-scope-organization-${key}`, "Organization member", provider.graphql.ownerAffiliations.includes("ORGANIZATION_MEMBER"))
               + this.check2html(`config-graphql-scope-collaborator-${key}`, "Collaborator", provider.graphql.ownerAffiliations.includes("COLLABORATOR")))

dashgit-web/app/WiViewHeaders.js

@@ -32,11 +32,11 @@ const wiHeaders = {
       return `
       <div style="padding-left:8px">
         <p class="mb-3 mt-2">
-          This view displayw all pull requests created by Dependabot.
+          This view displays all pull requests created by Dependabot.
           From this view, you can combine all updates into a sigle PR per repository and merge them automatically with just a few clicks.
         </p>
         <p class="mb-3 mt-2 text-danger">
-          To enable this feature, you have to check the configuration option <em>Enable a Manager Repository for advanced functions</em>,
+          To enable the combined updates feature, you have to check the configuration option <em>Enable a Manager Repository for advanced functions</em>,
           create the manager repository as indicated
           <a href="${config.param.readmeManagerRepo}" target="_blank">[here]</a>
           and follow instructions in this tab.
@@ -51,7 +51,7 @@ const wiHeaders = {
           you have to add a workflow file <code>.github/workflows/manage-updates.yml</code>.<br/>
           <a href="#" id="wi-update-workflow-file-show">Click here to get the required content and copy it to the workflow file</a>.<br/>
           Since no token is ever transmitted out of the browser, you also have to create the secrets indicated below in each provider
-          (storing an api access token to each one).
+          and store an API access token in each one.
         </p>
         <div id="wi-update-workflow-file-div" style="display: none">
           <a href="#" id="wi-update-workflow-file-hide">[Hide]</a>

dashgit-web/app/index.html

@@ -146,7 +146,7 @@ <h3> &nbsp; DashGit<span class="h5 d-none d-sm-inline"> - Dashboard for GitHub a
     <!-- target tabs -->
     <ul role="listitem" class="nav nav-tabs" id="tab-headers" role="tablist" style="display:none">
       <li class="nav-item" role="presentation" data-toggle="tooltip"
-        title="Open work items (issues/pull requests) where I'm the assignee or reviewer and follow up reminders">
+        title="Open work items (issues/pull requests) where I'm the assignee or reviewer, and follow up reminders">
         <button class="nav-link active" id="assigned-tab" data-bs-toggle="tab" data-bs-target="#assigned" type="button"
           role="tab" aria-controls="assigned" aria-selected="true">Assigned</button>
       </li>