jfairley / github-slack-bot Goto Github PK

Rather than issuing command keywords (channel foo or add snippet bar), offer message buttons with the "value" to follow as a plain comment.

1. What would you like to do?
   • Slack Channel
   • Add Snippet
   • Done
2. click Slack Channel
3. type foo, hit Enter

reference: https://api.slack.com/docs/message-buttons

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL git+https://github.com/jfairley/github-slack-bot.git.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀

I want to define snippets so that I can list them, but I don't want those snippets to trigger an direct message.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL http://[email protected]/jfairley/github-slack-bot.git.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀

It would be helpful to know how to setup the bot from the slack app side

instead of

Configured teams:
- U0XRT2V70

show the real username in some way.

What would be sweet is if I could get notified on any comment (even if they don't atNotify me) on a PR that I created. What happens now is that I'll create a PR and then if somebody comments on it without atNotifying me, I'll not get notified and miss the comment.

Along the same lines, I'm not sure this is possible but it would be cool to have another toggle for being notified on ANY PR that I've commented on even if I'm not atNotified. Sometimes I comment during a PR review and then somebody responds to me (but they don't atNotify me) and I miss the comment. Or, maybe I make a comment and then conversations happens around that comment and I miss it because none of that conversation atNotifies me.

Hope that all makes sense

As a github user I would like to be notified in slack whenever a label is added or removed from a pr

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

No npm token specified.

An npm token must be created and set in the NPM_TOKEN environment variable on your CI environment.

Please make sure to create an npm token and to set it in the NPM_TOKEN environment variable on your CI environment. The token must allow to publish to the registry https://registry.npmjs.org/.

Good luck with your project ✨

Your semantic-release bot 📦🚀

When someone requests a review, send a message.

🚨 The automated release from the master branch failed. 🚨

I recommend you give this issue a high priority, so other packages depending on you could benefit from your bug fixes and new features.

You can find below the list of errors reported by semantic-release. Each one of them has to be resolved in order to automatically publish your package. I’m sure you can resolve this 💪.

Errors are usually caused by a misconfiguration or an authentication problem. With each error reported below you will find explanation and guidance to help you to resolve it.

Once all the errors are resolved, semantic-release will release your package the next time you push a commit to the master branch. You can also manually restart the failed CI job that runs semantic-release.

If you are not sure how to resolve this, here is some links that can help you:

• Usage documentation
• Frequently Asked Questions
• Support channels

If those don’t help, or if this issue is reporting something you think isn’t right, you can always ask the humans behind semantic-release.

The push permission to the Git repository is required.

semantic-release cannot push the version tag to the branch master on remote Git repository with URL git+https://github.com/jfairley/github-slack-bot.git.

Please refer to the authentication configuration documentation to configure the Git credentials on your CI environment and make sure the repositoryUrl is configured with a valid Git URL.

Good luck with your project ✨

Your semantic-release bot 📦🚀

As an admin, I would like to be able to remove a team.

remove <team>

The bot should ask for confirmation before deleting a team.

When a slack channel is registered like #channel, the preceding # should be detected and parsed out.

Via configuration, I want to receive a direct message for all comments on a pull request or issue that I created.

Via configuration, I want to receive a direct message for all comments on a review that I created.

PRs post in the channel immediately. People ignore these messages, because they know the PR is not green

TODOs

• restrict S3 access permissions
• add some sort of auth filter based on slack token
• implement bot 😏

As a developer, I would like to be notified when a commit status is set on my PR. This activity typically represents CI job status or coverage status.

Somewhere, sometimes, the bot receives a JSON payload from Github that it can't handle. The exception causes the bot process to exit.

1. An error processing input should not crash the bot.
2. If the bot crashes, is there a configuration for PM2 that would automatically restore it?
   • Is there something other than PM2 that would work better to manage the node server?