Skip to content

Commit b206e87

Browse files
ZemerikZemerik
committed
Release: v1.0.2
1 parent 7c55b61 commit b206e87

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

44 files changed

+2525
-1044
lines changed

‎.github/ISSUE_TEMPLATE/bug.yml‎

Lines changed: 52 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
2+
3+
name: 🐞 Bug Report
4+
description: File a bug report
5+
title: '[Bug]: '
6+
labels: ['bug']
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thanks for taking the time to fill out this bug report!
12+
- type: textarea
13+
id: what-happened
14+
attributes:
15+
label: What happened?
16+
description: Also tell us, what did you expect to happen?
17+
placeholder: Add descriptions
18+
value: 'Briefly Describe the bug you found'
19+
validations:
20+
required: true
21+
- type: textarea
22+
id: screenshots
23+
attributes:
24+
label: Add screenshots
25+
description: Add screenshots to see the problems
26+
placeholder: Add screenshots
27+
value: 'Add screenshots'
28+
- type: dropdown
29+
id: browsers
30+
attributes:
31+
label: What browsers are you seeing the problem on?
32+
multiple: true
33+
options:
34+
- Firefox
35+
- Chrome
36+
- Safari
37+
- Microsoft Edge
38+
- Brave
39+
- Other
40+
- type: checkboxes
41+
id: self-grab
42+
attributes:
43+
label: Self - Grab
44+
description: By checking this box, you can fix this bug
45+
options:
46+
- label: I would like to work on this issue
47+
id: terms
48+
attributes:
49+
label: Code of Conduct
50+
description: By submitting this issue, you agree to follow our Code of Conduct
51+
options:
52+
- label: I agree to follow this project's Code of Conduct

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
2+
---
3+
name: Feature request
4+
about: Suggest an idea for this project
5+
title: ''
6+
labels: ''
7+
assignees: ''
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
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+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you've considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

‎.github/ISSUE_TEMPLATE/style.yml‎

Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
2+
3+
name: 👯‍♂️ Style Changing Request
4+
description: Suggest a style designs
5+
title: '[style]: '
6+
labels: ['enhancement']
7+
body:
8+
- type: markdown
9+
attributes:
10+
value: |
11+
Thanks for taking the time to fill out this template!
12+
- type: textarea
13+
id: style-idea
14+
attributes:
15+
label: What's the style idea?
16+
placeholder: Add descriptions
17+
value: 'We need to improve '
18+
validations:
19+
required: true
20+
- type: textarea
21+
id: screenshots
22+
attributes:
23+
label: Add screenshots
24+
description: Add screenshots to see the demo
25+
placeholder: Add screenshots
26+
value: 'Add screenshots'
27+
- type: checkboxes
28+
id: terms
29+
attributes:
30+
label: Code of Conduct
31+
description: By submitting this issue, you agree to follow our Code of Conduct
32+
options:
33+
- label: I agree to follow this project's Code of Conduct

‎.github/pull_request_template.md‎

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,30 @@
1+
2+
<!-- If your PR fixes an open issue, use `Closes #999` to link your PR with the issue. #999 stands for the issue number you are fixing -->
3+
4+
## Fixes Issue
5+
6+
<!-- Remove this section if not applicable -->
7+
8+
<!-- Example: Closes #31 -->
9+
10+
## Changes proposed
11+
12+
<!-- List all the proposed changes in your PR -->
13+
14+
<!-- Mark all the applicable boxes. To mark the box as done follow the following conventions -->
15+
<!--
16+
[x] - Correct; marked as done
17+
[X] - Correct; marked as done
18+
19+
[ ] - Not correct; marked as **not** done
20+
-->
21+
22+
## Check List (Check all the applicable boxes) <!-- Follow the above conventions to check the box -->
23+
24+
- [ ] My Changes follow the Code of Conduct of this Project.
25+
- [ ] My Post or Change does not contain any **Plagarized** Content.
26+
- [ ] The title of the PR is a short description of the Changes made.
27+
28+
## Note to reviewers
29+
30+
<!-- Add notes to reviewers if applicable -->

‎.github/workflows/greetings.yml‎

Lines changed: 40 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,40 @@
1+
2+
name: Greetings
3+
4+
on:
5+
pull_request:
6+
types: [opened]
7+
issues:
8+
types: [opened]
9+
10+
permissions:
11+
issues: write
12+
pull-requests: write
13+
14+
jobs:
15+
greet:
16+
runs-on: ubuntu-latest
17+
steps:
18+
- name: Greet on PRs and Issues
19+
uses: actions/github-script@v7
20+
with:
21+
script: |
22+
try {
23+
const isPR = context.payload.pull_request !== undefined;
24+
const number = isPR ? context.payload.pull_request.number : context.payload.issue.number;
25+
const commentBody = isPR
26+
? `Welcome, @${{ github.actor }}! Thanks for raising the issue!`
27+
: `Great job, @${{ github.actor }}! Thanks for creating the pull request`;
28+
29+
await github.rest.issues.createComment({
30+
owner: context.repo.owner,
31+
repo: context.repo.repo,
32+
issue_number: number,
33+
body: commentBody
34+
});
35+
36+
console.log('Comment successfully created.');
37+
} catch (error) {
38+
console.error('Error creating comment:', error);
39+
// Do not mark the step as failed; continue with the workflow.
40+
}

‎404.html‎

Lines changed: 53 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
<!DOCTYPE html>
2+
<html lang="en">
3+
<head>
4+
<meta charset="UTF-8">
5+
<meta name="viewport" content="width=device-width, initial-scale=1.0">
6+
7+
<!--=============== BOXICONS ===============-->
8+
<link href='https://unpkg.com/boxicons@2.1.2/css/boxicons.min.css' rel='stylesheet'>
9+
10+
<!--=============== CSS ===============-->
11+
<link rel="stylesheet" href="styles/css/404.css">
12+
13+
<link rel = "icon" href = "assets/config/icon.png" />
14+
15+
<title>404 - Hemang Yadav (Zemerik)</title>
16+
</head>
17+
<body>
18+
19+
<!--==================== MAIN ====================-->
20+
<main class="main">
21+
<!--==================== HOME ====================-->
22+
<section class="home">
23+
<div class="home__container container">
24+
<div class="home__data">
25+
<span class="home__subtitle">Error 404</span>
26+
<h1 class="home__title">Hey Buddy</h1>
27+
<p class="home__description">
28+
We can't seem to find the page <br> you are looking for.
29+
</p>
30+
<a href="https://zemerik.is-a.dev/" class="home__button">
31+
Go Home
32+
</a>
33+
</div>
34+
35+
<div class="home__img">
36+
<img src="assets/config/404.png" alt="">
37+
<div class="home__shadow"></div>
38+
</div>
39+
</div>
40+
41+
<footer class="home__footer">
42+
<span>zemerikY@gmail.com</span>
43+
</footer>
44+
</section>
45+
</main>
46+
47+
<!--=============== SCROLLREVEAL ===============-->
48+
<script src="scripts/scrollreveal.min.js"></script>
49+
50+
<!--=============== MAIN JS ===============-->
51+
<script src="scripts/main.js"></script>
52+
</body>
53+
</html>

‎CODE_OF_CONDUCT.md‎

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

0 commit comments

Comments
 (0)