* Adding the capability to create the approval issue in another repository
* reverting testing changes
* reverting test changes contd.
* Updating readme and removing a debug line
* Introduce a 'fail-on-denial' boolean (#147)
* Introduce a 'fail-on-approval' boolean
* Use test docker image
* oops
* change default and fix logic
* Update action.yaml
* Fix linting error
* Adding the capability to create the approval issue in another repository
* reverting testing changes
* reverting test changes contd.
* moving targetRepo inputs from env vars to action-args
* Update constants.go
* Update constants.go to resolve nuances created by inconsistent tab length settings
---------
Co-authored-by: Liz MacLean <18120837+lizziemac@users.noreply.github.com>
* Add new input 'issue-body'
Similar to the 'issue-title' input, 'issue-body' allows to put custom
text to the body of the approval issue.
* Update readme for 'issue-body' input
Currently if you have an org team name with a period in it, the team will not be found with a 404 response. This is because the GitHub API requires that the periods are replaced with hyphens. This PR fixes this behavior and closes#55.
Signed-off-by: Thomas Stringer <thomas@trstringer.com>
* Add documentation for team approver
This feature is now tested and this PR adds the necessary documentation
to show how to implement org team expansion for approvers.
Signed-off-by: Thomas Stringer <thomas@trstringer.com>
* fix action version
Signed-off-by: Thomas Stringer <thomas@trstringer.com>
Currently group expansion is failing. I suspect this is due to workflow
permissions, as this succeeds locally. This additional logging should
show unexpected errors that aren't just a non-group expansion.
Prior to this change, the approvers could only be explicit users. With
this change, you can now specify an org team and this will be expanded
out with a user list for approvers.
Closes#14.
If a required approver does not have the ability to be an approver in
the repository then when running this action you could receive an
HTTP/402 Validation Failed error. This change documents this behavior.
Closes#7.
If you want to be able to force a timeout for the manual approval
process you can use the `timeout-minutes` setting for either the step or
the job. This change documents this in the README. Closes#15.
* Adding support for custom titles.
* Cleaning up blank lines in main.go
* Renaming approvalIssueTitle to IssueTitle in all relavent places.
* Fixing period in README
Co-authored-by: Thomas Stringer <thomas@trstringer.com>
* Remove period in action doc.
Co-authored-by: Thomas Stringer <thomas@trstringer.com>
Co-authored-by: Thomas Stringer <thomas@trstringer.com>
Prior to this PR, if there was a newline (or multiple newline
characters) at the end of the keyword then it wouldn't match. With this
fix any number of newlines at the end of the keyword match will now be
considered for approve or deny.
This PR adds a debug logging statement to stdout prior to creating the
issue. This will help troubleshoot issues, such as a GitHub API http/422
response status with invalid message.
* Close issue if kill signal received
* Refactor: Exiting main loop can close application without explicit call to os.Exit(0)
* Leave a comment on the closed issue if the close handler is triggered
* Accidentally deleted the final logging command
* Fix punctuation on the closing comment
* Handle the comment loop and interruption handling via channels and a select statement
* Update main.go
