feat: Auto reviewer branch policy

[C123R]

Signed-off-by: Cizer Pereira mail@cizer.dev

All Submissions:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• My code follows the code style of this project.
• I ran lint checks locally prior to submission.
• Have you checked to ensure there aren't other open PRs for the same update/change?

What about the current behavior has changed?

Issue Number: #29

Does this introduce a change to go.mod, go.sum or vendor/?

• Yes
• No

Does this introduce a breaking change?

• Yes
• No

Any relevant logs, error output, etc?

(If it’s long, please paste to https://ghostbin.com/ and insert the link here.)

Other information

[EliiseS]

@C123R Thank you!

[C123R]

@C123R Thank you!

Awesome, @EliiseS Thanks for your support :)

Btw, there are other branch policies which we could add it as a resource. Should I create an issue first or directly come up with the PR?

[EliiseS]

@C123R An issue first, but more as a place of documentation, such as links to the API docs and design discussion 😄
Feel free to start working on it right away, just make a comment on the issue saying you're picking it up.