Skip to content

Commit 8e3021d

Browse files
technote-spacetechnote-space
committed
Initial commit
0 parents  commit 8e3021d

37 files changed

+4795
-0
lines changed

‎.github/CODEOWNERS

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
* @technote-space

‎.github/CODE_OF_CONDUCT.md

+76
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at [email protected]. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎.github/CONTRIBUTING.md

+33
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
# Contributing
2+
[issues]: https://github.com/technote-space/gh-actions-template/issues
3+
[fork]: https://github.com/technote-space/gh-actions-template/fork
4+
[pr]: https://github.com/technote-space/gh-actions-template/compare
5+
[jest]: https://jestjs.io/
6+
[code-of-conduct]: CODE_OF_CONDUCT.md
7+
8+
When contributing to this repository, please first discuss the change you wish to make via [issue][issues] with the owners of this repository before making a change.
9+
10+
Please note we have a [Contributor Code of Conduct][code-of-conduct], please follow it in all your interactions with the project.
11+
12+
## Submitting a pull request
13+
14+
1. [Fork][fork] and clone the repository
15+
1. Make sure the tests pass on your machine: `composer test`, which contains
16+
- [`Jest`][jest]
17+
1. Create a new branch: `git checkout -b my-branch-name`
18+
1. Make your change, add tests, and make sure the tests still pass.
19+
1. Push to your fork and [submit a pull request][pr].
20+
1. Pat your self on the back and wait for your pull request to be reviewed and merged.
21+
22+
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
23+
- Write and update tests.
24+
- Keep your change as focused as possible. If there are multiple changes you would like to make that are not dependent upon each other, consider submitting them as separate pull requests.
25+
- Write a [good commit message](https://github.com/erlang/otp/wiki/writing-good-commit-messages).
26+
27+
Work in Progress pull request are also welcome to get feedback early on, or if there is something blocked you.
28+
29+
## Resources
30+
31+
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
32+
- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
33+
- [GitHub Help](https://help.github.com)

‎.github/FUNDING.yml

+1
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
custom: https://paypal.me/technote0space

‎.github/ISSUE_TEMPLATE/bug_report.md

+37
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: 'technote-space'
7+
8+
---
9+
10+
## Describe the bug: バグの概要
11+
<!-- A clear and concise description of what the bug is. -->
12+
<!-- バグの内容を簡潔かつ明確に書いてください -->
13+
14+
## To Reproduce: 再現手順
15+
Steps to reproduce the behavior:
16+
1. Go to '...'
17+
2. Click on '....'
18+
3. Scroll down to '....'
19+
4. See error
20+
21+
## Expected behavior: 期待する動作
22+
<!-- A clear and concise description of what you expected to happen. -->
23+
<!-- あなたが期待する動きを簡潔かつ明確に書いてください -->
24+
25+
## Screenshots: スクリーンショット
26+
<!-- If applicable, add screenshots to help explain your problem. -->
27+
<!-- バグの説明に役立つスクリーンショットを用意できる場合、ここに追加してください -->
28+
29+
## Operating environment: バグが発生した環境
30+
- Version of software
31+
- OS: [e.g. Windows10]
32+
- Browser: [e.g. Chrome, Safari]
33+
- etc.
34+
35+
## Additional context: 補足
36+
<!-- Add any other context about the problem here. -->
37+
<!-- このバグに関連する情報を追加してください -->

‎.github/ISSUE_TEMPLATE/feature_request.md

+24
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: 'technote-space'
7+
8+
---
9+
10+
## Please describe your suggestion: 提案の概要
11+
<!-- A clear and concise description of what the problem is. e.g. I'm always frustrated when [...] -->
12+
<!-- 『～をするときにいつもイライラする』など、現在抱えている問題の概要 -->
13+
14+
## Describe the solution you'd like: 考えうる解決方法
15+
<!-- A clear and concise description of what you want to happen. -->
16+
<!-- こう動けばイライラが解消するなど、期待する動作の概要 -->
17+
18+
## Describe alternatives you've considered: 考えうる代替案
19+
<!-- A clear and concise description of any alternative solutions or features you've considered. -->
20+
<!-- あなたが考えたり試したことのある代替方法 -->
21+
22+
## Additional context: 補足
23+
<!-- Add any other context or screenshots about the feature request here. -->
24+
<!-- 補足やスクリーンショットなど -->

‎.github/card-labeler.yml

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
Backlog:
2+
'In progress':
3+
- 'Status: In Progress'

‎.github/config.yml

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# Configuration for request-info - https://github.com/behaviorbot/request-info
2+
3+
# *Required* Comment to reply with
4+
requestInfoReplyComment: >
5+
:clap: We would appreciate it if you could provide us with more info about this issue/pr!
6+
7+
# *OPTIONAL* default titles to check against for lack of descriptiveness
8+
# MUST BE ALL LOWERCASE
9+
requestInfoDefaultTitles:
10+
- update readme.md
11+
- updates
12+
- update
13+
14+
# *OPTIONAL* Label to be added to Issues and Pull Requests with insufficient information given
15+
requestInfoLabelToAdd: "Status: More Information Needed"
16+
17+
18+
19+
20+
# Configuration for welcome - https://github.com/behaviorbot/welcome
21+
22+
# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
23+
24+
# Comment to be posted to on first time issues
25+
newIssueWelcomeComment: >
26+
:raised_hands: Thanks for opening your first issue here! Be sure to follow the issue template!
27+
28+
# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
29+
30+
# Comment to be posted to on PRs from first time contributors in your repository
31+
newPRWelcomeComment: >
32+
:raised_hands: Thanks for opening this pull request! Please check out our contributing guidelines.
33+
34+
# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
35+
36+
# Comment to be posted to on pull requests merged by a first time user
37+
firstPRMergeComment: >
38+
:tada: Congrats on merging your first pull request! We here at behaviorbot are proud of you!
39+
40+
41+
42+
# Configuration for todo - https://github.com/jasonetco/todo
43+
todo:
44+
- label: "Type: Todo"

‎.github/labeler.yml

+15
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,15 @@
1+
javascript:
2+
- '**/*.js'
3+
typescript:
4+
- '**/*.ts'
5+
dependencies:
6+
- '**/*.lock'
7+
- '**/*-lock.json'
8+
9+
'Type: Testing':
10+
- '**/tests/*'
11+
- '**/test/*'
12+
- '**/__tests__/*'
13+
14+
'Type: Documentation':
15+
- '**/*.md'

‎.github/no-response.yml

+13
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
# Configuration for probot-no-response - https://github.com/probot/no-response
2+
3+
# Number of days of inactivity before an Issue is closed for lack of response
4+
daysUntilClose: 30
5+
# Label requiring a response
6+
responseRequiredLabel: "Status: More Information Needed"
7+
# Comment to post when closing an Issue for lack of response. Set to `false` to disable
8+
closeComment: >
9+
This issue has been automatically closed because there has been no response
10+
to our request for more information from the original author. With only the
11+
information that is currently in the issue, we don't have enough information
12+
to take action. Please reach out if you have or find the answers we need so
13+
that we can investigate further.

‎.github/pr-labeler.yml

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
'Type: Feature': ['feature/*', 'feat/*']
2+
'Type: Bug': fix/*
3+
'Type: Maintenance': ['patch/*', 'chore/*']
4+
'Type: Release': release/*
5+
'Type: Refactoring': ['refactor/*', 'refactoring/*']
6+
'Type: Documentation': ['docs/*', 'doc/*']

‎.github/pull_request_template.md

+19
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,19 @@
1+
## Description: 概要
2+
<!-- Please describe purpose of change or related Issue number -->
3+
<!-- 変更の目的 もしくは 関連する Issue 番号 -->
4+
5+
## Changes: 変更内容
6+
<!-- Detail of changes (please add screenshots if applicable) -->
7+
<!-- ビューの変更がある場合はスクショによる比較などがあるとわかりやすい -->
8+
9+
## Expected Impact: 影響範囲
10+
<!-- e.g. I changed this function, which might be affect that function. -->
11+
<!-- この関数を変更したのでこの機能にも影響がある、など -->
12+
13+
## Operating Requirements: 動作要件
14+
<!-- e.g. Environment variables / Dependencies / DB updates -->
15+
<!-- 動作に必要な 環境変数 / 依存関係 / DBの更新 など -->
16+
17+
## Additional context: 補足
18+
<!-- e.g. Point or review / Cautions when trying in a local environment -->
19+
<!-- レビューをする際に見てほしい点、ローカル環境で試す際の注意点、など -->

‎.github/release-drafter.yml

+28
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# Config for https://github.com/apps/release-drafter
2+
name-template: 'v$NEXT_PATCH_VERSION'
3+
tag-template: 'v$NEXT_PATCH_VERSION'
4+
categories:
5+
- title: ':rocket: Features'
6+
labels:
7+
- 'Type: Feature'
8+
- 'Type: Refactoring'
9+
- title: ':bug: Bug Fixes'
10+
labels:
11+
- 'Type: Bug'
12+
- 'Type: Security'
13+
- title: ':wrench: Maintenance'
14+
labels:
15+
- 'Type: Maintenance'
16+
- title: ':green_book: Docs'
17+
labels:
18+
- 'Type: Documentation'
19+
- title: ':white_check_mark: Tested'
20+
labels:
21+
- 'Type: Testing'
22+
- title: ':sparkles: All Changes'
23+
labels:
24+
- 'Type: Release'
25+
template: |
26+
## What’s Changed
27+
28+
$CHANGES

‎.github/stale.yml

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# Number of days of inactivity before an issue becomes stale
2+
daysUntilStale: 180
3+
# Number of days of inactivity before a stale issue is closed
4+
daysUntilClose: 30
5+
# Issues with these labels will never be considered stale
6+
exemptLabels:
7+
- "Priority: Critical"
8+
- "Type: Security"
9+
# Label to use when marking an issue as stale
10+
staleLabel: "Status: Abandoned"
11+
# Comment to post when marking an issue as stale. Set to `false` to disable
12+
markComment: >
13+
This issue has been automatically marked as stale because it has not had
14+
recent activity. It will be closed if no further activity occurs. Thank you
15+
for your contributions.
16+
# Comment to post when closing a stale issue. Set to `false` to disable
17+
closeComment: false

‎.github/workflows/ci.yml

+44
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
on:
2+
pull_request:
3+
push:
4+
branches:
5+
- master
6+
tags:
7+
- "!*"
8+
9+
name: Build
10+
11+
jobs:
12+
jest:
13+
name: Jest
14+
runs-on: ubuntu-latest
15+
steps:
16+
- uses: actions/checkout@v1
17+
with:
18+
fetch-depth: 1
19+
- name: Install Package dependencies
20+
run: yarn install
21+
- name: Run tests
22+
run: yarn cover
23+
- name: Send covarage
24+
run: yarn add coveralls && cat ./coverage/lcov.info | ./node_modules/coveralls/bin/coveralls.js
25+
env:
26+
COVERALLS_REPO_TOKEN: ${{ secrets.COVERALLS_REPO_TOKEN }}
27+
COVERALLS_SERVICE_NAME: "GitHub Action"
28+
COVERALLS_SERVICE_JOB_ID: ${{ github.sha }}
29+
COVERALLS_GIT_COMMIT: ${{ github.sha }}
30+
COVERALLS_GIT_BRANCH: ${{ github.ref }}
31+
- uses: 8398a7/action-slack@v1
32+
with:
33+
type: failure
34+
env:
35+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
36+
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
37+
if: failure()
38+
- uses: 8398a7/action-slack@v1
39+
with:
40+
type: success
41+
env:
42+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
43+
SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}
44+
if: success()

‎.github/workflows/gh_releases.yml

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
on:
2+
push:
3+
branches:
4+
- master
5+
name: GitHub Releases
6+
jobs:
7+
draftRelease:
8+
name: Draft Release
9+
runs-on: ubuntu-latest
10+
steps:
11+
- name: Draft Release
12+
uses: toolmantim/[email protected]
13+
env:
14+
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

0 commit comments

Comments
 (0)