Skip to content

Conversation

@jarlungoodoo73
Copy link

@jarlungoodoo73 jarlungoodoo73 commented Jan 30, 2026

### Motivation

Change description

Other information

Reviewer checklist

  • PR addresses a single concern.
  • The PR has no duplicates (please search among the Pull Requests before creating one)
  • PR title and description are properly filled.
  • Docs have been added / updated (for bug fixes / features)
    Semantic-action.yml (2).txt
Copilot AI review requested due to automatic review settings January 30, 2026 13:37
@jarlungoodoo73
Copy link
Author

@copilot # Requesting a pull request review

After you create a pull request, you can ask a specific person to review the changes you've proposed. If you're an organization member, you can also request a specific team to review your changes.

Repositories belong to a personal account (a single individual owner) or an organization account (a shared account with numerous collaborators or maintainers). For more information, see Types of GitHub accounts. Owners and collaborators on a repository owned by a personal account can assign pull request reviews. Organization members with triage permissions can also assign a reviewer for a pull request.

To assign a reviewer to a pull request, you will need write access to the repository. For more information about repository access, see Repository roles for an organization. If you have write access, you can assign anyone who has read access to the repository as a reviewer.

Organization members with write access can also assign a pull request review to any person or team with read access to a repository. The requested reviewer or team will receive a notification that you asked them to review the pull request. If you request a review from a team and code review assignment is enabled, specific members will be requested and the team will be removed as a reviewer. For more information, see Managing code review settings for your team.

Note

Pull request authors can't request reviews unless they are either a repository owner or collaborator with write access to the repository.

Requesting reviews from collaborators and organization members

You can request a review from either a suggested or specific person. Suggested reviewers are based on git blame data. If you request a review, other people with read access to the repository can still review your pull request. Once someone has reviewed your pull request and you've made the necessary changes, you can re-request review from the same reviewer. If the requested reviewer does not submit a review, and the pull request meets the repository's mergeability requirements, you can still merge the pull request.

  1. Under your repository name, click Pull requests.

    Screenshot of the main page of a repository. In the horizontal navigation bar, a tab, labeled "Pull requests," is outlined in dark orange.

  2. In the list of pull requests, click the pull request that you'd like to ask a specific person or a team to review.

  3. To request a review from a suggested person under Reviewers, next to their username, click Request.

    Screenshot of the "Reviewers" section of a pull request's sidebar. To the right of @octocat, a "Request" link is outlined in dark orange.

  4. Optionally, to request a review from someone other than a suggested person, click Reviewers.

    If you know the name of the person or team you'd like a review from, type the username of the person or the name of the team you're asking to review your changes. Click their team name or username to request a review.

  5. After your pull request is reviewed and you've made the necessary changes, you can ask a reviewer to re-review your pull request. Navigate to Reviewers in the right sidebar and click next to the reviewer's name whose review you'd like.

    Screenshot of the "Reviewers" section of a pull request's sidebar. To the right of @octocat, a sync icon is outlined in dark orange.

Requesting a review from GitHub Copilot

You can also request that Copilot reviews your code and provides feedback and suggested changes on your work. See Using GitHub Copilot code review.

Further reading

Copy link
Author

@jarlungoodoo73 jarlungoodoo73 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Waiting approval, check code if complete without errors

Copy link
Author

@jarlungoodoo73 jarlungoodoo73 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approval Git

Copy link

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

@per1234 per1234 self-assigned this Jan 30, 2026
Copy link
Collaborator

@per1234 per1234 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jarlungoodoo73 please stop making pointless pull requests and comments in Arduino's repositories.

The resources available to maintain this free open source software are finite. We are forced to expend resources cleaning up your mess instead of doing productive work that would benefit the entire open source community.

If you want to experiment using GitHub, do that in repositories under your own account.

If you continue this behavior, I will be forced to report you to GitHub, which may result in the termination of your account.

@per1234 per1234 closed this Jan 30, 2026
@per1234 per1234 added the conclusion: invalid Issue/PR not valid label Jan 30, 2026
@arduino arduino locked as off-topic and limited conversation to collaborators Jan 30, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

conclusion: invalid Issue/PR not valid

2 participants