Skip to content

Commit 8e592b5

Browse files
committed
feat(templates): open source repo
1 parent a2d88ae commit 8e592b5

16 files changed

+665
-1
lines changed

.github/FUNDING.yml

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# These are supported funding model platforms
2+
3+
github: [monacodelisa]
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
name: 🐛 Bug report
2+
description: Create a bug report to help us improve AnguHashBlog
3+
title: "Bug: "
4+
labels: [👀 needs triage, 🐛 bug]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thanks for taking the time to fill out this bug report!
10+
- type: textarea
11+
attributes:
12+
label: Describe the bug
13+
description: A clear and concise description of what the bug is.
14+
validations:
15+
required: true
16+
- type: textarea
17+
attributes:
18+
label: Steps to reproduce
19+
description: Describe how to reproduce the behavior.
20+
placeholder: |
21+
1. Go to '...'
22+
2. Click on '...'
23+
3. Scroll down to '...'
24+
4. See error
25+
validations:
26+
required: true
27+
- type: dropdown
28+
attributes:
29+
multiple: true
30+
label: Browsers
31+
description: Select the browsers where the issue can be reproduced (that you know of).
32+
options:
33+
- "Chrome"
34+
- "Firefox"
35+
- "Safari"
36+
- "Edge"
37+
- "Opera"
38+
- "Other (add additional context)"
39+
- type: input
40+
id: context
41+
attributes:
42+
label: Additional context (Is this in dev or production?)
43+
description: Add any other context about the problem or helpful links here.
44+
45+
- type: checkboxes
46+
id: assistance
47+
attributes:
48+
label: I would be willing to submit a PR to fix this issue
49+
description: Assistance is provided if you need help submitting a pull request
50+
options:
51+
- label: "Yes and I have read the [Contribution Guide](https://anguhashblog.com/contributing) and I agree to follow this project's [Code of Conduct](https://anguhashblog.com/code-of-conduct)"
52+
- label: 'No'

.github/ISSUE_TEMPLATE/config.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,5 @@
1+
blank_issues_enabled: false
2+
contact_links:
3+
- name: ❓ Ask a question
4+
url: https://discord.com/invite/h3JXbADsBy
5+
about: Ask questions about open source onboarding
Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
name: 🚀 Feature request
2+
description: Suggest an idea for this project 💡
3+
title: "Feature: "
4+
labels: [👀 needs triage, 💡 feature]
5+
body:
6+
- type: markdown
7+
attributes:
8+
value: |
9+
Thanks for taking the time to fill out this feature request!
10+
- type: dropdown
11+
attributes:
12+
multiple: false
13+
label: Type of feature
14+
description: Select the type of feature request, the lowercase should also be the PR prefix.
15+
options:
16+
- "✨ Feature"
17+
- "🐛 Fix"
18+
- "📝 Documentation"
19+
- "🎨 Style"
20+
- "🧑‍💻 Refactor"
21+
- "🔥 Performance"
22+
- "✅ Test"
23+
- "🤖 Build"
24+
- "🔁 CI"
25+
- "📦 Chore"
26+
- "⏩ Revert"
27+
validations:
28+
required: true
29+
- type: textarea
30+
attributes:
31+
label: Current behavior
32+
description: Is your feature request related to a problem? Please describe.
33+
validations:
34+
required: true
35+
- type: textarea
36+
attributes:
37+
label: Suggested solution
38+
description: Describe the solution you'd like.
39+
- type: input
40+
id: context
41+
attributes:
42+
label: Additional context
43+
description: Add any other context about the problem or helpful links here.
44+
45+
- type: checkboxes
46+
id: assistance
47+
attributes:
48+
label: I would be willing to submit a PR to fix this issue
49+
description: Assistance is provided if you need help submitting a pull request
50+
options:
51+
- label: "Yes and I have read the [Contribution Guide](https://anguhashblog.com/contributing) and I agree to follow this project's [Code of Conduct](https://anguhashblog.com/code-of-conduct)"
52+
- label: 'No'

.github/PULL_REQUEST_TEMPLATE.md

Lines changed: 34 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,34 @@
1+
2+
## This PR Closes Issue
3+
closes #
4+
5+
## Description
6+
7+
## What type of PR is this? (check all applicable)
8+
9+
- [ ] 🅰️ Feature
10+
- [ ] 🐛 Bug Fix
11+
- [ ] 📝 Documentation Update
12+
- [ ] 🎨 Style
13+
- [ ] 🧑‍💻 Code Refactor
14+
- [ ] 🔥 Performance Improvements
15+
- [ ] ✅ Test
16+
- [ ] 🤖 Build
17+
- [ ] 🔁 CI
18+
- [ ] 📦 Chore (Release)
19+
- [ ] ⏩ Revert
20+
21+
## Mobile & Desktop Screenshots/Recordings
22+
[Attach screenshots or recordings if applicable]
23+
24+
## Steps to QA
25+
26+
## Added to documentation?
27+
- [ ] 📜 README.md
28+
- [ ] 🙅 no documentation needed
29+
30+
## [Optional] Post-deployment tasks
31+
[Specify any post-deployment tasks that need to be performed]
32+
33+
## [Optional] What gif best describes this PR or how it makes you feel?
34+
[Embed gif or describe the feeling in plain text]

.github/workflows/issue.yml

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
# This workflow posts an automated comment on every new issue
2+
# https://github.com/marketplace/actions/create-or-update-comment (https://github.com/peter-evans/create-or-update-comment)
3+
4+
name: Automatic Comment
5+
on:
6+
issues:
7+
types: [opened]
8+
permissions:
9+
contents: read
10+
11+
jobs:
12+
comment:
13+
permissions:
14+
issues: write # for peter-evans/create-or-update-comment to create or update comment
15+
pull-requests: write # for peter-evans/create-or-update-comment to create or update comment
16+
name: Comment
17+
runs-on: ubuntu-latest
18+
steps:
19+
- name: Automatic Comment
20+
uses: peter-evans/create-or-update-comment@v2
21+
with:
22+
issue-number: ${{ github.event.issue.number }}
23+
body: |
24+
Thanks for the issue, our team will look into it as soon as possible! If you would like to work on this issue, please wait for us to decide if it's ready. The issue will be ready to work on once we remove the "needs triage" label.
25+
26+
To claim an issue that does not have the "needs triage" label, please leave a comment that says ".take". If you have any questions, please reach out to us on [Discord](https://discord.gg/SQCFCACz) or follow up on the issue itself.
27+
28+
For full info on how to contribute, please check out our [contributors guide](https://anguhashblog.com/contributing).

.github/workflows/triage.yml

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,21 @@
1+
name: "Assign issues with .take"
2+
3+
on:
4+
issue_comment:
5+
types:
6+
- created
7+
- edited
8+
9+
jobs:
10+
take-issue:
11+
name: Disable take issue
12+
runs-on: ubuntu-latest
13+
timeout-minutes: 10
14+
steps:
15+
- name: take an issue
16+
uses: bdougie/take-action@v1.6.1
17+
with:
18+
issueCurrentlyAssignedMessage: Thanks for being interested in this issue. It looks like this ticket is already assigned to a contributor.
19+
token: ${{ secrets.ACCESS_TOKEN }}
20+
blockingLabels: 👀 needs triage,blocked,core team work,📛 prerequisites missing,needs design,duplicate
21+
blockingLabelsMessage: The issue you are trying to assign yourself is blocked either by the 'needs triage' label, or by another label on the issue. Please wait until the issue is unblocked before assigning yourself.

CODE_OF_CONDUCT.md

Lines changed: 128 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,128 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
We as members, contributors, and leaders pledge to make participation in our
6+
community a harassment-free experience for everyone, regardless of age, body
7+
size, visible or invisible disability, ethnicity, sex characteristics, gender
8+
identity and expression, level of experience, education, socio-economic status,
9+
nationality, personal appearance, race, religion, or sexual identity
10+
and orientation.
11+
12+
We pledge to act and interact in ways that contribute to an open, welcoming,
13+
diverse, inclusive, and healthy community.
14+
15+
## Our Standards
16+
17+
Examples of behavior that contributes to a positive environment for our
18+
community include:
19+
20+
* Demonstrating empathy and kindness toward other people
21+
* Being respectful of differing opinions, viewpoints, and experiences
22+
* Giving and gracefully accepting constructive feedback
23+
* Accepting responsibility and apologizing to those affected by our mistakes,
24+
and learning from the experience
25+
* Focusing on what is best not just for us as individuals, but for the
26+
overall community
27+
28+
Examples of unacceptable behavior include:
29+
30+
* The use of sexualized language or imagery, and sexual attention or
31+
advances of any kind
32+
* Trolling, insulting or derogatory comments, and personal or political attacks
33+
* Public or private harassment
34+
* Publishing others' private information, such as a physical or email
35+
address, without their explicit permission
36+
* Other conduct which could reasonably be considered inappropriate in a
37+
professional setting
38+
39+
## Enforcement Responsibilities
40+
41+
Community leaders are responsible for clarifying and enforcing our standards of
42+
acceptable behavior and will take appropriate and fair corrective action in
43+
response to any behavior that they deem inappropriate, threatening, offensive,
44+
or harmful.
45+
46+
Community leaders have the right and responsibility to remove, edit, or reject
47+
comments, commits, code, wiki edits, issues, and other contributions that are
48+
not aligned to this Code of Conduct, and will communicate reasons for moderation
49+
decisions when appropriate.
50+
51+
## Scope
52+
53+
This Code of Conduct applies within all community spaces, and also applies when
54+
an individual is officially representing the community in public spaces.
55+
Examples of representing our community include using an official e-mail address,
56+
posting via an official social media account, or acting as an appointed
57+
representative at an online or offline event.
58+
59+
## Enforcement
60+
61+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
62+
reported to the community leaders responsible for enforcement at
63+
monacodelisa@gmail.com.
64+
All complaints will be reviewed and investigated promptly and fairly.
65+
66+
All community leaders are obligated to respect the privacy and security of the
67+
reporter of any incident.
68+
69+
## Enforcement Guidelines
70+
71+
Community leaders will follow these Community Impact Guidelines in determining
72+
the consequences for any action they deem in violation of this Code of Conduct:
73+
74+
### 1. Correction
75+
76+
**Community Impact**: Use of inappropriate language or other behavior deemed
77+
unprofessional or unwelcome in the community.
78+
79+
**Consequence**: A private, written warning from community leaders, providing
80+
clarity around the nature of the violation and an explanation of why the
81+
behavior was inappropriate. A public apology may be requested.
82+
83+
### 2. Warning
84+
85+
**Community Impact**: A violation through a single incident or series
86+
of actions.
87+
88+
**Consequence**: A warning with consequences for continued behavior. No
89+
interaction with the people involved, including unsolicited interaction with
90+
those enforcing the Code of Conduct, for a specified period of time. This
91+
includes avoiding interactions in community spaces as well as external channels
92+
like social media. Violating these terms may lead to a temporary or
93+
permanent ban.
94+
95+
### 3. Temporary Ban
96+
97+
**Community Impact**: A serious violation of community standards, including
98+
sustained inappropriate behavior.
99+
100+
**Consequence**: A temporary ban from any sort of interaction or public
101+
communication with the community for a specified period of time. No public or
102+
private interaction with the people involved, including unsolicited interaction
103+
with those enforcing the Code of Conduct, is allowed during this period.
104+
Violating these terms may lead to a permanent ban.
105+
106+
### 4. Permanent Ban
107+
108+
**Community Impact**: Demonstrating a pattern of violation of community
109+
standards, including sustained inappropriate behavior, harassment of an
110+
individual, or aggression toward or disparagement of classes of individuals.
111+
112+
**Consequence**: A permanent ban from any sort of public interaction within
113+
the community.
114+
115+
## Attribution
116+
117+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
118+
version 2.0, available at
119+
https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
120+
121+
Community Impact Guidelines were inspired by [Mozilla's code of conduct
122+
enforcement ladder](https://github.com/mozilla/diversity).
123+
124+
[homepage]: https://www.contributor-covenant.org
125+
126+
For answers to common questions about this code of conduct, see the FAQ at
127+
https://www.contributor-covenant.org/faq. Translations are available at
128+
https://www.contributor-covenant.org/translations.

0 commit comments

Comments
 (0)