Skip to content

Commit 6875a5f

Browse files
ZemerikZemerik
committed
Code. Learn. Repeat. Python Edition
0 parents  commit 6875a5f

File tree

10 files changed

+698
-0
lines changed

10 files changed

+698
-0
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md‎

Lines changed: 36 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,36 @@
1+
---
2+
name: 🐛 Bug Report
3+
about: Report unexpected behavior or errors
4+
title: "[BUG] "
5+
labels: bug
6+
---
7+
8+
## Describe the Bug
9+
A clear and concise description of what's wrong.
10+
11+
## To Reproduce
12+
Steps to reproduce the behavior:
13+
1. Go to '...'
14+
2. Run '....'
15+
3. See error
16+
17+
## Expected Behavior
18+
What should normally happen?
19+
20+
## Screenshots/Code Snippets
21+
22+
```python
23+
# Add problematic code if applicable
24+
```
25+
26+
## Environment
27+
28+
- Python Version: [e.g. 3.9.7]
29+
30+
- OS: [e.g. Windows 11]
31+
32+
- Affected Files: [e.g. Day 5/functions.py]
33+
34+
## Additional Context
35+
36+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/documentation.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
---
2+
name: 📖 Documentation
3+
about: Report unclear/missing documentation
4+
title: "[DOCS] "
5+
labels: documentation
6+
---
7+
8+
## Affected Files
9+
Which README/code comments need improvement?
10+
11+
## Current State
12+
What's unclear or missing?
13+
14+
## Suggested Improvement
15+
How should we clarify this?
16+
17+
## Additional Context
18+
Add examples if possible

‎.github/ISSUE_TEMPLATE/feature_request.md‎

Lines changed: 24 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,24 @@
1+
---
2+
name: 🚀 Feature Request
3+
about: Suggest an enhancement or new content
4+
title: "[FEATURE] "
5+
labels: enhancement
6+
---
7+
8+
## Feature Description
9+
What concept/exercise should we add or improve?
10+
11+
## Why Is This Valuable?
12+
How does this help learners?
13+
14+
## Proposed Implementation
15+
(Optional) Suggest how to implement:
16+
- Files to create/modify
17+
- Code examples
18+
- Documentation updates
19+
20+
## Alternative Approaches
21+
Any other ways to achieve this?
22+
23+
## Additional Context
24+
Add sketches/diagrams if helpful

‎.github/pull_request_template.md‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
# Pull Request Overview
2+
3+
## Description
4+
What does this PR change/fix/add?
5+
6+
## Related Issues
7+
Closes # (issue number(s))
8+
9+
## Checklist
10+
- [ ] Code follows PEP 8 style guide
11+
- [ ] Documentation (README/comments) updated
12+
- [ ] No commented-out debug code
13+
- [ ] New files have descriptive names
14+
- [ ] Tests added/updated (if applicable)
15+
16+
## Verification Steps
17+
How did you test these changes?
18+
1. Ran `python ...`
19+
2. Checked output for ...
20+
3. Verified documentation rendering
21+
22+
## Screenshots
23+
(Add before/after if UI-related)
24+
25+
## Additional Notes
26+
Anything else maintainers should know?

‎.github/workflows/greetings.yml‎

Lines changed: 22 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
name: 'Greetings'
2+
3+
on:
4+
fork:
5+
push:
6+
branches: [main]
7+
issues:
8+
types: [opened]
9+
pull_request_target:
10+
types: [opened]
11+
12+
jobs:
13+
welcome:
14+
runs-on: ubuntu-latest
15+
steps:
16+
- uses: actions/checkout@v1
17+
- uses: EddieHubCommunity/gh-action-community/src/welcome@main
18+
with:
19+
github-token: ${{ secrets.GITHUB_TOKEN }}
20+
issue-message: 'Welcome, @${{ github.actor }}! Thanks for raising the issue!'
21+
pr-message: 'Great job, @${{ github.actor }}! Thanks for creating the pull request!'
22+
footer: 'Soon the maintainers/owner will review it and provide you with feedback/suggestions. 👍 Rember to leave a ⭐!'

‎CODE_OF_CODUCT.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+
zemerikY@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)