Aviator's Chrome Extension | Aviator Documentation

Aviator's Chrome Extension offers a few capabilities: MergeQueue - You can enqueue / dequeue your pull-request from GitHub, monitor the status and review the stack. AttentionSet - Track all the PRs that require your attention. On the GitHub page for the PR, you can also toggle the attention. Installation Install from Chrome Web Store . After the installation, open your pull-request, and you can find a log-in button instead of the GitHub merge button. Click the login button, and you'll redirected to the Aviator login page. If you are already logged in, it should automatically get back to the original PR page. The browser extension is also supported on Arc. Pinning the extension Once installed, you can optionally pin the Chrome extension. This way, whenever there's a PR that require your attention, it will show you a red badge within your browser. Connecting with GitHub To enable the AttentionSet in Chrome Extension, you need to connect your Aviator user with GitHub user. You can find that configuration in Settings > Personal > Integrations , or follow this link . How to use AttentionSet The extension shows you the list of PRs that require your attention. These may be PRs that require a review from you, or the PRs authored by you that are waiting for your action after a response from the reviewer. If you pin the extension to Chrome, it will show the number of PRs that require your attention as a badge. On clicking the icon, it expands a popup view that lists those PRs Any PR that is approved and ready to merge shows up with a green bar. On the PR details page, you can also view and toggle the Attention for the GitHub users from the right side menu. MergeQueue If the repository is configured with Aviator MergeQueue, it shows a button to enqueue a pull request. This will work properly with stacked PRs as well. Enqueue an open PR Once the PR has entered the queue, the extension will show information about the bot pull request, and a timeline of the PR's activity. If the queue is currently paused, the extension will notify the user, regardless of the PR's status. PR in the merge queue The extension will show updated information if the PR is blocked. Blocked PR If you need, there is an option to show the original GitHub merge button. Use with Aviator MergeQueue on-prem You can open the extension option page from the extension menu. You can specify your on-prem Aviator deployment URL. Previous Aviator CLI v0.1.0 Release Notes Next Pilot Automated Actions Last updated 1 year ago Was this helpful?

The technical content provided is mostly clear, but there are a few minor issues and areas for improvement:

1. Grammar and Punctuation:

   • "Click the login button, and you'll redirected to the Aviator login page." should be "Click the login button, and you'll be redirected to the Aviator login page."
   • "whenever there's a PR that require your attention" should be "whenever there's a PR that requires your attention."
   • "To enable the AttentionSet in Chrome Extension" should be "To enable the AttentionSet in the Chrome Extension."
   • "On clicking the icon, it expands a popup view that lists those PRs" should be "Upon clicking the icon, it expands a popup view that lists those PRs."
   • "If you need, there is an option to show the original GitHub merge button." could be improved to "If needed, there is an option to show the original GitHub merge button."

2. Clarity and Consistency:

   • The phrase "MergeQueue - You can enqueue / dequeue your pull-request from GitHub, monitor the status and review the stack." could be clearer. Consider rephrasing to "MergeQueue - You can enqueue or dequeue your pull request from GitHub, monitor its status, and review the stack."
   • The section "Use with Aviator MergeQueue on-prem" could be more explicit. It might be helpful to specify what "on-prem" means for users who might not be familiar with the term.

3. Formatting:

   • The "Installation" section mentions "Install from Chrome Web Store." This could be formatted as a hyperlink if it's intended to be a clickable link.
   • Similarly, "follow this link" in the "Connecting with GitHub" section should be formatted as a hyperlink if it is meant to direct users to a specific URL.

4. Technical Details:

   • Ensure that the instructions for connecting the Aviator user with the GitHub user are clear and complete. If there are specific steps or permissions required, they should be detailed.
   • The document mentions "Aviator MergeQueue" and "AttentionSet" without explaining what they are. A brief description or link to more detailed documentation would be helpful for users unfamiliar with these terms.

Overall, the content is informative, but addressing these issues will improve clarity and user experience.

No product messaging analysis available for this page.

No competitive analysis available for this page.