chore: fix lint

Author: OmriBarZik

.github/ISSUE_TEMPLATE/bug_report.md

@@ -4,14 +4,14 @@ about: Create a report to help us improve
 title: ''
 labels: ''
 assignees: ''
-
 ---
 
 **Describe the bug**
 A clear and concise description of what the bug is.
 
 **To Reproduce**
 Steps to reproduce the behavior:
+
 1. Go to '...'
 2. Click on '....'
 3. Scroll down to '....'
@@ -24,15 +24,17 @@ A clear and concise description of what you expected to happen.
 If applicable, add screenshots to help explain your problem.
 
 **Desktop (please complete the following information):**
- - OS: [e.g. iOS]
- - Browser [e.g. chrome, safari]
- - Version [e.g. 22]
+
+- OS: [e.g. iOS]
+- Browser [e.g. chrome, safari]
+- Version [e.g. 22]
 
 **Smartphone (please complete the following information):**
- - Device: [e.g. iPhone6]
- - OS: [e.g. iOS8.1]
- - Browser [e.g. stock browser, safari]
- - Version [e.g. 22]
+
+- Device: [e.g. iPhone6]
+- OS: [e.g. iOS8.1]
+- Browser [e.g. stock browser, safari]
+- Version [e.g. 22]
 
 **Additional context**
 Add any other context about the problem here.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -4,7 +4,6 @@ about: Suggest an idea for this project
 title: ''
 labels: ''
 assignees: ''
-
 ---
 
 **Is your feature request related to a problem? Please describe.**

.github/auto_assign.yml

@@ -5,7 +5,7 @@ addReviewers: true
 addAssignees: true
 
 # A list of reviewers to be added to pull requests (GitHub user name)
-reviewers: 
+reviewers:
   - MichalPorag
   - ozizhakGT
   - abrl91

.github/workflows/e2e-ci.yml

@@ -1,4 +1,4 @@
-name: "Tests: E2E"
+name: 'Tests: E2E'
 on: [pull_request]
 jobs:
   tests_e2e:

.github/workflows/tests.yml

@@ -22,7 +22,7 @@ jobs:
         with:
           node-version: 16
           cache: 'npm'
-      
+
       - name: Install dependencies
         run: npm ci
 

CODE_OF_CONDUCT.md

@@ -20,28 +20,28 @@ If you see someone who is making an extra effort to ensure our community is welc
 
 The following behaviors are expected and requested of all community members:
 
- * Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
- * Exercise consideration and respect in your speech and actions.
- * Attempt collaboration before conflict.
- * Refrain from demeaning, discriminatory, or harassing behavior and speech.
- * Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
- * Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
+- Participate in an authentic and active way. In doing so, you contribute to the health and longevity of this community.
+- Exercise consideration and respect in your speech and actions.
+- Attempt collaboration before conflict.
+- Refrain from demeaning, discriminatory, or harassing behavior and speech.
+- Be mindful of your surroundings and of your fellow participants. Alert community leaders if you notice a dangerous situation, someone in distress, or violations of this Code of Conduct, even if they seem inconsequential.
+- Remember that community event venues may be shared with members of the public; please be respectful to all patrons of these locations.
 
 ## 4. Unacceptable Behavior
 
 The following behaviors are considered harassment and are unacceptable within our community:
 
- * Violence, threats of violence or violent language directed against another person.
- * Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
- * Posting or displaying sexually explicit or violent material.
- * Posting or threatening to post other people's personally identifying information ("doxing").
- * Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
- * Inappropriate photography or recording.
- * Inappropriate physical contact. You should have someone's consent before touching them.
- * Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
- * Deliberate intimidation, stalking or following (online or in person).
- * Advocating for, or encouraging, any of the above behavior.
- * Sustained disruption of community events, including talks and presentations.
+- Violence, threats of violence or violent language directed against another person.
+- Sexist, racist, homophobic, transphobic, ableist or otherwise discriminatory jokes and language.
+- Posting or displaying sexually explicit or violent material.
+- Posting or threatening to post other people's personally identifying information ("doxing").
+- Personal insults, particularly those related to gender, sexual orientation, race, religion, or disability.
+- Inappropriate photography or recording.
+- Inappropriate physical contact. You should have someone's consent before touching them.
+- Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
+- Deliberate intimidation, stalking or following (online or in person).
+- Advocating for, or encouraging, any of the above behavior.
+- Sustained disruption of community events, including talks and presentations.
 
 ## 5. Weapons Policy
 
@@ -59,15 +59,11 @@ If a community member engages in unacceptable behavior, the community organizers
 
 If you are subject to or witness unacceptable behavior, or have any other concerns, please notify a community organizer as soon as possible. miporagi@gmail.com.
 
-
-
 Additionally, community organizers are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.
 
 ## 8. Addressing Grievances
 
-If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify Pull-Request-Community with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies. 
-
-
+If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify Pull-Request-Community with a concise description of your grievance. Your grievance will be handled in accordance with our existing governing policies.
 
 ## 9. Scope
 
@@ -81,7 +77,7 @@ miporagi@gmail.com
 
 ## 11. License and attribution
 
-The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/). 
+The Citizen Code of Conduct is distributed by [Stumptown Syndicate](http://stumptownsyndicate.org) under a [Creative Commons Attribution-ShareAlike license](http://creativecommons.org/licenses/by-sa/3.0/).
 
 Portions of text derived from the [Django Code of Conduct](https://www.djangoproject.com/conduct/) and the [Geek Feminism Anti-Harassment Policy](http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy).
 

README.md

@@ -88,7 +88,6 @@ npm run dev
 
 Open [http://localhost:3000](http://localhost:3000) with your browser to see the result.
 
+# Contributing to the project:
 
-
-# Contributing to the project: 
 If you are interested in contributing to the project, please follow this [guide](https://github.com/Pull-Request-Community/pull-request-community-website/blob/master/docs/contributing.md).

docs/contributing.md

@@ -1,22 +1,25 @@
 # Contribution To The Pull Request Website
+
 Thank you, it is not obvious that you are devoting your time to contributing to our community.
 We appreciate it very much.❤️🙏🏻
 
 Before jumping into the deep water, it's essential to discuss a bit of communication.
 One of the biggest challenges on each project (especially on open-source projects) is communication.
 Good communication can lead to great achievements, effective teamwork, time efficiency and make the working process fun and easy.
-It is important to remember that all contributions are made voluntarily by people that devote their time and hard work. We are all part of a team, so *please be passionate and polite to each other*.
+It is important to remember that all contributions are made voluntarily by people that devote their time and hard work. We are all part of a team, so _please be passionate and polite to each other_.
 
 Please follow this guide to make your experience as pleasant and easy as possible.
 
 ## The Ways You Can Contribute To The Pull Request Website:
-* Opening a [new issue](https://github.com/Pull-Request-Community/pull-request-community-website/issues/new) with a bug or a feature proposal.
-* Add documentation for existing features.
-* Improvement of our tests.
-* Solving an issue or adding a new feature.
+
+- Opening a [new issue](https://github.com/Pull-Request-Community/pull-request-community-website/issues/new) with a bug or a feature proposal.
+- Add documentation for existing features.
+- Improvement of our tests.
+- Solving an issue or adding a new feature.
 
 ## The Preferred Way To Contribute:
-1. Pick an issue from the [issues list](https://github.com/Pull-Request-Community/pull-request-community-website/issues) or [open a new issue](https://github.com/Pull-Request-Community/pull-request-community-website/issues/new) and *ask*, by writing a new comment on the issue's page, to own the task.
+
+1. Pick an issue from the [issues list](https://github.com/Pull-Request-Community/pull-request-community-website/issues) or [open a new issue](https://github.com/Pull-Request-Community/pull-request-community-website/issues/new) and _ask_, by writing a new comment on the issue's page, to own the task.
 2. Wait for the maintainer's ownership approval. Keep in mind that they may not approve that. Like we said at the beggining, communication is everything.
 3. Fork the project. For more details, please read this article: [My first contribution to open source: Make a fork of the repo / Galen Corey](https://opensource.com/article/19/11/first-open-source-contribution-fork-clone).
 4. Clone the forked project to your local machine (see instructions below).
@@ -25,21 +28,26 @@ Please follow this guide to make your experience as pleasant and easy as possibl
 7. While working on an issue, feel free to ask any questions on the issue's page.
 8. Open pull request (make sure you open the pull requset on the original project and not on the forked project).
 9. Make sure all the tests are passing.
-10. Merge to the *main* branch.
+10. Merge to the _main_ branch.
 
-## Working On Issue: 
-Having a clear work flow of code development can be very useful. Therefore, please work on branches that are linked to a relevant issue. 
+## Working On Issue:
+
+Having a clear work flow of code development can be very useful. Therefore, please work on branches that are linked to a relevant issue.
 Don't you know how to connect a branch to an issue? no problem, follow this [guid](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-a-branch-for-an-issue).
- 
+
 ## Developing In A Branch:
+
 Please make sure you follow this list:
-1) Link your branch to the relevant issue.
-2) Use meaningful names for commits.
-3) Create small commits for each logic unit at a time.
-4) Use a [tasks list](https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists) to manage your work.
+
+1. Link your branch to the relevant issue.
+2. Use meaningful names for commits.
+3. Create small commits for each logic unit at a time.
+4. Use a [tasks list](https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists) to manage your work.
 
 ## TSX Specifications:
+
 Please follow this functional component pattern:
+
 ```
 interface Props {
   prop: <type>

e2e/home.spec.ts

@@ -1,8 +1,7 @@
-import { test, expect } from '@playwright/test'
+import { test, expect } from '@playwright/test';
 
-test('page should have title of "קהילת Pull Request"', async ({page}) => {
-    await page.goto('http://localhost:3000/')
-    const title = await page.title()
-    expect(title).toBe('קהילת Pull Request')
+test('page should have title of "קהילת Pull Request"', async ({ page }) => {
+  await page.goto('http://localhost:3000/');
+  const title = await page.title();
+  expect(title).toBe('קהילת Pull Request');
 });
-

people/AdirSlutzki.json

@@ -5,4 +5,4 @@
   "linkedin": "https://www.linkedin.com/in/adir-slutzki-1686189",
   "twitter": "https://twitter.com/adircode",
   "description": "מעצב UI/UX ומאסטר ב-CSS מרצה במכללות ברחבי הארץ ומכין שקשוקה מעולה, אוהב לעשות אנימציות ופרויקטים אישיים."
-}
+}