Skip to content

Approvers are not verified against required approvers for environment #182

@JakubBiel

Description

@JakubBiel
  • I have searched through the current issues and did not find any that were related.

Describe the bug
From readme

  • approvers is a comma-delimited list of all required approvers. An approver can either be a user or an org team. (Note: Required approvers must have the ability to be set as approvers in the repository. If you add an approver that doesn't have this permission then you would receive an HTTP/402 Validation Failed error when running this action)

This is a bit misleading. My understanding of it was that approvers are verified against required approvers for the environment the action runs in. This is however not the case and anyone with write permissions to the repository is able to approve when passed in approvers.

Expected behavior
A user that doesn't have permissions to approve a workflow should not be able to do so.

Metadata

Metadata

Assignees

No one assigned

    Labels

    documentationImprovements or additions to documentationenhancementNew feature or request

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions