actionsdesk / behest Goto Github PK

Getting this down so I don't forget it.

The action.yml file is missing the teams input and looks like it could be updated for this action in a couple other ways.

https://github.com/ActionsDesk/behest/blob/master/action.yml

We found a small bug when running /issuescreate. If we don't specify a message or template name, we still pass the action but it throws an error which doesn't result in the action failing. Really we should check if a message or template name is actually passed and otherwise throw an error and fail the action.

The error looks like:

(node:2424) UnhandledPromiseRejectionWarning: Error: EISDIR: illegal operation on a directory, read
    at Object.readSync (fs.js:506:3)
    at tryReadSync (fs.js:331:20)
    at Object.readFileSync (fs.js:368:19)
    at Object.<anonymous> (/home/runner/work/_actions/wenlock/behest/wenlock-add-commands/dist/index.js:6357:23)
    at Generator.next (<anonymous>)
    at fulfilled (/home/runner/work/_actions/wenlock/behest/wenlock-add-commands/dist/index.js:6265:58)

I'm hoping to have a little time this week to fix that.

Another common issue we run into is making repos private/public/internal. It would be nice to add that action to our list of commands

Would it be useful to have commands similar to Dependabot?

Scenario

I want to invite a user to the org and close out the issue where the request is made.

By using the /invite command in the comment I would need to later close the issue when the invite is successful. This format will also limit me to use one command at a time to affect an issue.

Suggestion

/behest <command> and <command>, this way we can string together commands that could effect the issue.

Eg. /behest invite and close, would do the same as /invite with the added outcome of closing the issue when invite is successful.

This functionality might open a bunch of other commands that could be useful later on like:

• /behest reopen and assign @froi - reopen an issue and assign it to the specified user