Skip to content

Wrong scope of commits #811

Description

@dmitrytrager

Considering I have a branch br in up-to-date state and PR N from br to master.
If master includes commit h violating linter rules, it should not be reported since PR commits do not include it.
Sometimes it is reported however.
This problem goes away when some other PR M is merged and br is updated accordingly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions