Skip to content

Commit

Permalink
initial commit
Browse files Browse the repository at this point in the history
  • Loading branch information
Eun committed Jul 26, 2021
0 parents commit efa04de
Show file tree
Hide file tree
Showing 7,009 changed files with 883,882 additions and 0 deletions.
The diff you're trying to view is too large. We only load the first 3000 changed files.
18 changes: 18 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
## Description

## Problem
A short description of the problem this PR is addressing.

## Solution
A short description of the chosen method to resolve the problem
with an overview of the logic and implementation details when needed.

## Notes
Other notes that you want to share but do not fit into _Problem_ or _Solution_.

### Checklist
- [ ] The title starts either with `feat:`, `fix:`, or `chore:`
- `feat` should be used if this pull request implements a new feature
- `fix` should be used if this pull request fixes a bug
- `chore` should be used for maintenance changes

28 changes: 28 additions & 0 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
version: 2
updates:
- package-ecosystem: "npm"
open-pull-requests-limit: 10
directory: "/"
schedule:
interval: daily
time: "04:00"
commit-message:
prefix: "chore"
labels:
- "dependencies"
- "node"
- "chore"

- package-ecosystem: "github-actions"
open-pull-requests-limit: 10
directory: "/"
schedule:
interval: "daily"
time: "04:00"
commit-message:
prefix: "chore"
labels:
- "dependencies"
- "github_actions"
- "chore"

8 changes: 8 additions & 0 deletions .github/labeler.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,8 @@
labels:
'feature':
- '^(?i:feat)'
- '^(?i:feature)'
'fix':
- '^(?i:fix)'
'chore':
- '^(?i:chore)'
38 changes: 38 additions & 0 deletions .github/release-drafter.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,38 @@
name-template: 'v$RESOLVED_VERSION'
tag-template: 'v$RESOLVED_VERSION'
categories:
- title: '🚀 Features'
label: 'feature'
- title: '🐛 Bug Fixes'
label: 'fix'
- title: '🧰 Maintenance'
label: 'chore'
change-template: '- $TITLE @$AUTHOR (#$NUMBER)'
change-title-escapes: '\<*_&' # You can add # and @ to disable mentions, and add ` to disable code blocks.
version-resolver:
major:
labels:
- 'major'
minor:
labels:
- 'minor'
patch:
labels:
- 'patch'
default: patch
autolabeler:
- label: 'feature'
title:
- '/^feat/i'
- '/^feature/i'
- label: 'fix'
title:
- '/^fix/i'
- label: 'chore'
title:
- '/^chore/i'
template: |
## Changes
$CHANGES
17 changes: 17 additions & 0 deletions .github/workflows/pull_request_target_opened.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
# this workflow will run on all pull requests opened but in the context of the base of the pull request.
on:
pull_request_target:
types: [opened]

name: "pull_request_target_opened"
jobs:
# labeler will label pull requests based on their title.
# the configuration is at .github/labeler.yml.
label_pull_request:
runs-on: ubuntu-latest
steps:
-
name: Label Pull Request
uses: jimschubert/labeler-action@v2
with:
GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
28 changes: 28 additions & 0 deletions .github/workflows/push.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
# this workflow will run on all pushes.
on:
push:

name: "push"
jobs:
test:
runs-on: ubuntu-latest
steps:
-
name: Checkout code
uses: actions/checkout@v2
-
uses: actions/setup-node@v2
-
run: npm run test

# draft your next release notes as pull requests are merged into "master"
# the configuration is at /.github/release-drafter.yml.
update_release_draft:
runs-on: ubuntu-latest
steps:
- uses: release-drafter/release-drafter@v5
if: github.ref == 'refs/heads/master'
with:
config-name: release-drafter.yml
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
/coverage
7 changes: 7 additions & 0 deletions LICENSE
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
Copyright 2021 Talon.One GmbH

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
44 changes: 44 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,44 @@
# clubhouse-move-story-action
---
GitHub Action to move Clubhouse Stories to another workflow state after a github release was published.

## Inputs
### `github-token`
GitHub token (to read pull requests)

### `clubhouse-token`
Clubhouse Token (to read and move stories)

### `to-state`
A JSON object that defines where stories should be moved to.

### `pr-regex`
A regex expression to find the pull request number inside the github release body.
Note that this regular expression runs for every line in the release body.
Use the capture group `pr` to find the pull request number, the simplest expression would be `#(?<pr>\d+)`.

## Example
```yaml
# this workflow runs when a release was published.
on:
release:
types: [published]

name: "release_published"
jobs:
# Build the binary using GoReleaser
move-deployed-stories-to-completed:
runs-on: ubuntu-latest
steps:
-
uses: talon-one/clubhouse-move-story-action@v1
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
clubhouse-token: ${{ secrets.CLUBHOUSE_TOKEN }}
to-state: |
{
"Workflow 1": "Completed",
"Workflow 2": "Deployed"
}
pr-regex: '#(?<pr>\d+)'
```
23 changes: 23 additions & 0 deletions action.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,23 @@
# https://help.github.com/en/articles/metadata-syntax-for-github-actions
name: 'clubhouse-move-story-action'
description: 'GitHub Action to move Clubhouse Stories to another workflow state'
author: 'Talon.One GmbH'
branding:
icon: 'server'
color: 'blue'
inputs:
github-token:
description: 'GitHub token'
required: true
clubhouse-token:
description: 'Clubhouse token'
required: true
to-state:
description: 'A JSON object that defines where stories should be moved to.'
required: true
pr-regex:
description: 'A regex expression to find the pull request number inside the github release body.'
required: true
runs:
using: 'node12'
main: 'main.js'
Loading

0 comments on commit efa04de

Please sign in to comment.