Skip to content

Conversation

@graywolf336
Copy link
Contributor

Right now an incoming integration can be triggered with a regular GET request and if there is no script to trigger then the result is an empty message which is undesirable.

@graywolf336 graywolf336 merged commit 89372c1 into develop Apr 10, 2018
@graywolf336 graywolf336 deleted the incoming-integrations branch April 10, 2018 14:58
trongthanh added a commit to goalifyplus/Goalify.Chat that referenced this pull request Apr 16, 2018
* goalify: (42 commits)
  Add Reload as global object
  update setup script domain to subdomain to setup S3 bucket
  [OTHER] Post to redhat registries api when tagging new release (RocketChat#10414)
  add setting Goalify API Gateway and Goalify API Token
  update initialSetting script to seed 1 time only
  Fix and improve vietnamese translation (RocketChat#10397)
  Don't expose the 'settings' property on users to regular users via the rest api (RocketChat#10411)
  [FIX] Updated OpenShift Template to take an Image as a Param (RocketChat#9946)
  Use Node 8.9 for CI build
  Fix incoming integrations being able to trigger a new message with a GET if there is no script enabled (RocketChat#9576)
  Update allowed labels by the rocket.cat gh bot (RocketChat#10360)
  [FIX] Snaps installations are breaking on avatar requests
  Update PULL_REQUEST_TEMPLATE.md
  Bump version to 0.64.0-develop
  Bump version to 0.63.1
  update dev apn key and cert
  Lower cased the first letter and removed unnecessary minus
  Fix: Incorrect French language usage for Disabled
  snap revert to 8.9.4
  Update saml_utils.js
  ...
@rodrigok rodrigok mentioned this pull request Apr 28, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants