Configure Clubhouse to respond to GitHub events by specific users.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
src
test
.env.dist
.eslintrc.js
.gitignore
.travis.yml
README.md
index.js
jest.config.js
package.json
prettier.config.js
yarn.lock

README.md

github-to-clubhouse

Build Status code style: prettier

Clubhouse's GitHub integration is great! Unfortunately, not all of my team agreed with that assessment. With this micro-service, you can configure Clubhouse to respond to GitHub events from a subset of users rather than every user.

  • Creating a branch moves the associated ticket to "in dev".
  • Opening a pull request moves the associated ticket to "awaiting code review".
  • Merging a pull requests moves the associated ticket to "in QA".

Usage

  1. Clone this repository.
  2. cp .env.dist .env
  3. Configure .env to your liking.
  4. Deploy your project to your chosen host.
  5. Configure a GitHub webhook for your repository pointing to your deployed project that sends at least the following events.
    • Branch or tag creation
    • Branch or tag deletion
    • Issue comments
    • Pull requests
    • Pushes
  6. Utilize the branch names provided by Clubhouse.

Resources