Home CodeReview

CodeReview

AI-powered review of your code, instantly actionable.
By Vishwesh
• 24 articles

How do I choose a pull request to review?

Short Answer: On Choose what you want to review select Review pull request, pick GitHub account and Repository, then pick a Pull request from Select pull request and click Continue. PreRequisites 1. Connected GitHub account (see Connect GitHub) 2. Repository contains at least one pull request accessible to your account Steps 1. On the Choose what you want to review page ensure the Review pull request tab is selected. Review pull request tab is active and fields are visible. 2. Open GitHub account and choose the account under GitHub account. Selected account (for example personal-account) is shown in the GitHub account field. 3. Open Repository and select the repository you want to review. Repository name (for example personal-website) appears in the Repository field. 4. Open Pull request → Select pull request, use the Search pull requests... box if needed, then choose the PR from the list. The selected Pull request is displayed in the Pull request field. 5. Click Continue to proceed to Select files to review. You are taken to the Select files to review screen. Troubleshooting 1. Continue is disabled (button greyed out). LikelyCause: Required fields (GitHub account, Repository, or Pull request) are not selected. Action: Select GitHub account, Repository and a Pull request. The Continue button becomes enabled after all required fields are set. 2. Pull request list is empty. LikelyCause: The selected repository has no pull requests or your account lacks access. Action: Verify the repository has PRs on GitHub and reconnect the correct GitHub account if needed. Note: You can switch to the Review branch / files tab to pick files manually instead of picking a PR.

Last updated on Jan 08, 2026

How do I select specific files to include in the review?

Short Answer: On Select files to review use the Pick my own files selector, the Search files... field, or the file-tree checkboxes to pick files, then click Run code review. PreRequisites 1. You have selected a Pull request or branch so files are available 2. Connected GitHub account with repo access Steps 1. On the Select files to review page locate Choose files to review. You see the file chooser area and a Search files... field or a mode dropdown (for example Pick my own files). 2. Open the file selector mode (e.g., Pick my own files) and use Search files... to filter by filename if needed. Matching files and folders appear in the file list. 3. Expand folders with the caret and toggle checkboxes next to files or folders to include them in the review. Checked files are selected; the summary line updates with the number of files selected. 4. Confirm the selection by checking the summary line (for example '3 files'). Summary reflects current selection and estimated cost. 5. Click Run code review to start the review for the selected files. Review starts, or a Low balance modal appears if you lack credits. Troubleshooting 1. The file list shows a spinner and never finishes loading. LikelyCause: Fetching files from GitHub is delayed due to network/GitHub API or permission issues. Action: Wait a moment, refresh the page, or reconnect GitHub. Confirm you have repository access. 2. Some checkboxes are disabled or files cannot be selected. LikelyCause: The file type is not supported for review or the file is already in review. Action: Hover the status icon to see the tooltip and exclude unsupported files or wait for the in-progress review to complete. Note: Only selected files will be included in the review; use search and folder checkboxes to efficiently include or exclude files.

Last updated on Jan 08, 2026

How do I connect Everdone to GitHub to run code reviews?

Short Answer: On the Run code review page choose a connection method (“Github App (Recommended)” or “Github OAuth”) and click “Connect GitHub” to authorize read-only access. PreRequisites 1. Signed in to Everdone 2. Access to the GitHub account you want to connect 3. If installing “Github App (Recommended)” you may need organization owner or admin access. Steps 1. Open the Run code review page and locate the “Connect to GitHub” box. Page shows “Run code review” header and connection options. 2. Choose a connection method: click “Github App (Recommended)” or “Github OAuth.” Selected option is highlighted and its description is visible (for example: “requires organization owner or admin access to install.” or “no admin rights needed.”). 3. Click the blue “Connect GitHub” button. GitHub authorization flow starts (GitHub sign-in/permission prompt). 4. Complete the GitHub authorization and grant read-only access. After authorizing you’ll be able to select repositories and branches (see “Choose what you want to review.”) Troubleshooting 1. Can’t install “Github App (Recommended).” LikelyCause: You are not an organization owner/admin; the card text notes it “requires organization owner or admin access to install.” Action: Select “Github OAuth” instead (the card text: “no admin rights needed”) or ask an organization owner/admin to install the app. 2. Authorization popup doesn’t appear or is blocked. LikelyCause: Browser blocked pop-ups or redirects. Action: Allow pop-ups for this site, then click “Connect GitHub” again. Note: Use “Github App (Recommended)” for teams when an admin can install it; use “Github OAuth” for personal access without admin rights.

Last updated on Jan 08, 2026

How do I pick which files are included in the review?

Short Answer: On “Select files to review” set “Choose files to review” to “Pick my own files,” use “Search files...” or expand the file tree to check files, confirm the summary line, then click “Run code review.” PreRequisites 1. Repository and Branch selected 2. Connected GitHub account 3. File list loaded Steps 1. Open the “Select files to review” page. Header “Select files to review” and the “Choose files to review” control are visible. 2. Ensure the “Choose files to review” dropdown reads “Pick my own files.” Dropdown set to “Pick my own files.” 3. Use the “Search files...” box to filter files, or expand folders in the file tree. Matching files are shown in the list. 4. Check the boxes next to files you want to include. Checked files are added to the selection (checkbox shows selected). 5. Confirm the selection summary under the file list (for example: “12 files selected”). Summary updates to reflect selected files and estimated cost. 6. Click “Run code review.” Either the review starts or a “Low balance” modal appears if funds are insufficient. Troubleshooting 1. No files are listed and the message reads “No files available for this repo/branch under the selected filter. Try another filter or branch.” LikelyCause: The current branch/filter does not include reviewable files. Action: Change the filter, switch branch, or try “Review pull request.” 2. A spinner displays and files do not appear. LikelyCause: Files are still loading due to network or server delay. Action: Wait a few moments for the spinner to finish, or refresh the page if it takes too long. 3. Some files show an icon or tooltip indicating they are not supported or already reviewed. LikelyCause: That file type is not supported or the file already has a review/in-progress run. Action: Hover the file to read the tooltip and avoid selecting unsupported files; wait for in-progress reviews to finish. Note: Only the files you select will be included in the review; unsupported files are indicated by a tooltip.

Last updated on Jan 08, 2026

What do the file status tooltips mean (for example 'Not reviewed yet' or 'Review already available')?

Short Answer: Hover files in the file list to see status tooltips such as 'This file type is not supported for review', 'Not reviewed yet. Select to start reviewing.', 'Review already available for this file.', and 'This file is already in review.' PreRequisites 1. File list visible 2. Hover-capable device (mouse or long-press on touch) Steps 1. Open 'Select files to review' and hover a file or its icon. A tooltip with the file state appears. 2. Read the tooltip text exactly. Examples shown in the UI include: You will see one of the messages: 'This file type is not supported for review', 'Not reviewed yet. Select to start reviewing.', 'Review already available for this file.', 'This file is already in review. You'll be able to regenerate once the current process completes.' and 'Review for this repository is in progress. You can start a new run once it is completed.' 3. Follow the tooltip guidance: don't select unsupported files, select 'Not reviewed yet' files to include them, or wait if a file/repository is currently in review. You understand each file's current state before selecting it. Troubleshooting 1. A file displays 'This file is already in review. You'll be able to regenerate once the current process completes.' LikelyCause: A review run for that file is currently in progress. Action: Wait for the current run to complete; then you can regenerate or start a new run for that file.

Last updated on Jan 08, 2026

How do I share a code review from an issue?

Short Answer: Open the Issue Level View, click “Share code review”, choose recipients in the modal, then confirm to send the review. PreRequisites 1. Signed in 2. Access to the repository and the specific PR/issue 3. Permission to share reviews Steps 1. Open the PR/issue so the Issue Level View is visible. Issue Level View with code and actions is displayed. 2. Click the “Share code review” button or action in the issue header. A “Share code review” modal appears. 3. In the “Share code review” modal, select people or teams to share with and set any visible permissions. Recipients and permissions are selected. 4. Click the modal’s primary action (e.g., “Share” or “Save”) to send the review. The modal closes and the review is shared with selected recipients. Troubleshooting 1. No users or teams appear in the modal when typing a name. LikelyCause: Directory search may be slow or the user is not in your organization. Action: Wait a few seconds for results, type full email/username, or confirm the user is in your organization. 2. The “Share” button is disabled. LikelyCause: No recipient selected, required fields empty, or you lack share permission. Action: Select at least one recipient and check permissions. If you still can’t, ask a repo admin to grant share rights. Note: The “Share code review” modal lists recipients and any available permission toggles — choose recipients carefully to avoid over-sharing.

Last updated on Jan 08, 2026