Skip to content
This repository was archived by the owner on Sep 2, 2022. It is now read-only.

Commit b71b989

Browse files
committed
📦 Init
0 parents  commit b71b989

23 files changed

+4091
-0
lines changed

.editorconfig

Lines changed: 9 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
root = true
2+
3+
[*]
4+
indent_style = space
5+
indent_size = 2
6+
end_of_line = lf
7+
charset = utf-8
8+
trim_trailing_whitespace = true
9+
insert_final_newline = true

.eslintignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
dist/

.eslintrc.json

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
{
2+
"parserOptions": {
3+
"ecmaVersion": 2020,
4+
"sourceType": "script"
5+
},
6+
"env": {
7+
"es6": true,
8+
"node": true
9+
},
10+
"plugins": ["github"],
11+
"extends": ["plugin:github/recommended"],
12+
"rules": {
13+
"camelcase": ["error", {"allow": [""]}],
14+
"no-console": "error"
15+
}
16+
}
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
---
2+
name: 'Bug report'
3+
about: 'Create a bug report to help improve this project'
4+
title: 'PLEASE DESCRIBE THE BUG'
5+
labels: 'bug :bug:'
6+
assignees: ''
7+
---
8+
9+
### Describe the bug
10+
11+
A clear and concise description of what the bug is.
12+
13+
### To Reproduce
14+
15+
Steps to reproduce the behavior:
16+
17+
1. Run '...'
18+
2. See error
19+
20+
### Expected behavior
21+
22+
A clear and concise description of what you expected to happen.
23+
24+
### Additional context
25+
26+
Add any other context about the problem here.

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
blank_issues_enabled: false
2+
3+
contact_links:
4+
- name: GitHub Professional Services
5+
url: https://services.github.com/#contact
6+
about: Contact GitHub Professional Services
Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: 'Feature request'
3+
about: 'Suggest an idea for this project'
4+
title: 'PLEASE DESCRIBE THE FEATURE REQUEST'
5+
labels: 'feature-request :construction:'
6+
assignees: ''
7+
---
8+
9+
### Is your feature request related to a problem? Please describe.
10+
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
### Describe the solution you'd like
14+
15+
A clear and concise description of what you want to happen.
16+
17+
### Describe alternatives you've considered
18+
19+
A clear and concise description of any alternative solutions or features you've considered.
20+
21+
### Additional context
22+
23+
Add any other context or screenshots about the feature request here.

.github/code_of_conduct.md

Lines changed: 76 additions & 0 deletions
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 make 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 within all project spaces, and it also applies when
49+
an individual is representing the project or its community in public spaces.
50+
Examples of representing a project or community include using an official
51+
project e-mail address, posting via an official social media account, or acting
52+
as an appointed representative at an online or offline event. Representation of
53+
a project may be 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 opensource@github.com. 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](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](https://www.contributor-covenant.org/faq)

.github/codeowners

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,2 @@
1+
# default owners
2+
* @ActionsDesk/services-delivery @stoe

.github/contributing.md

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
# Contributing
2+
3+
:wave: Hi there!
4+
We're thrilled that you'd like to contribute to this project. Your help is essential for keeping it great.
5+
6+
## Submitting a pull request
7+
8+
[Pull Requests][pulls] are used for adding new playbooks, roles, and documents to the repository, or editing the existing ones.
9+
10+
**With write access**
11+
12+
1. Clone the repository (only if you do not have write access)
13+
1. Create a new branch: `git checkout -b my-branch-name`
14+
1. Make your change
15+
1. Push and [submit a pull request][pr]
16+
1. Pat yourself on the back and wait for your pull request to be reviewed and merged.
17+
18+
**Without write access**
19+
20+
1. [Fork][fork] and clone the repository
21+
1. Create a new branch: `git checkout -b my-branch-name`
22+
1. Make your change
23+
1. Push to your fork and [submit a pull request][pr]
24+
1. Pat your self on the back and wait for your pull request to be reviewed and merged.
25+
26+
Here are a few things you can do that will increase the likelihood of your pull request being accepted:
27+
28+
- 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.
29+
- Write [good commit messages](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
30+
31+
Work in Progress pull requests are also welcome to get feedback early on, or if there is something blocking you.
32+
33+
- Create a branch with a name that identifies the user and nature of the changes (similar to `user/branch-purpose`)
34+
- Open a pull request and request a review from the `@github/ps-delivery` team
35+
36+
## Releasing
37+
38+
If you are the current maintainer of this action:
39+
40+
1. Create a [Tag](https://stackoverflow.com/questions/18216991/create-a-tag-in-a-github-repository)
41+
2. Draft [Release](https://help.github.com/en/github/administering-a-repository/managing-releases-in-a-repository) document explaining details of Release
42+
3. Look for approval from [CODEOWNERS](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners)
43+
44+
## Resources
45+
46+
- [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
47+
- [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
48+
- [GitHub Help](https://help.github.com)
49+
50+
[pulls]: https://github.com/github/github-demo-stack/pulls
51+
[pr]: https://github.com/github/github-demo-stack/compare
52+
[fork]: https://github.com/github/github-demo-stack/fork

.github/dependabot.yml

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
version: 2
2+
updates:
3+
- package-ecosystem: 'github-actions'
4+
directory: '/'
5+
schedule:
6+
interval: 'daily'
7+
commit-message:
8+
prefix: '🆙 github-action'
9+
labels:
10+
- 'github-action :robot:'
11+
12+
- package-ecosystem: 'npm'
13+
directory: '/'
14+
schedule:
15+
interval: 'daily'
16+
commit-message:
17+
prefix: '🆙 npm'
18+
include: 'scope'
19+
labels:
20+
- 'dependency :robot:'

0 commit comments

Comments
 (0)