You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+42-42Lines changed: 42 additions & 42 deletions
Original file line number
Diff line number
Diff line change
@@ -26,8 +26,8 @@ Look at the project and if you see some points which can be improved (it can be
26
26
27
27
For start working on the project you can use any of options from the below:
28
28
29
-
-You can set up project locally. This is **highly recommended** for regular/repeat contributions. This setup allows you to work and test your changes.
30
-
-Use Gitpod, a free online dev environment. Clicking the link below will start a ready-to-code dev environment in your browser. It only takes a few minutes.
29
+
- You can set up project locally. This is **highly recommended** for regular/repeat contributions. This setup allows you to work and test your changes.
30
+
- Use Gitpod, a free online dev environment. Clicking the link below will start a ready-to-code dev environment in your browser. It only takes a few minutes.
31
31
32
32
Click [here](https://gitpod.io/#https://github.com/hasadna/open-bus-map-search) to
33
33
open project in Gitpod
@@ -42,48 +42,48 @@ Follow these steps to run the project on your local machine:
42
42
2.**Clone the Repository:**
43
43
Clone the repository to your local machine. You can do this by running the following command in your terminal:
Once the repository is cloned, navigate to the project directory by running:
51
51
52
-
```bash
53
-
cd open-bus-map-search
54
-
```
52
+
```bash
53
+
cd open-bus-map-search
54
+
```
55
55
56
56
4.**Install Dependencies:**
57
57
The project uses npm to manage dependencies. Once Node is installed, you can install the project dependencies by running:
58
-
```bash
59
-
npm install
60
-
```
58
+
```bash
59
+
npm install
60
+
```
61
61
5.**Run the Project:**
62
62
After all dependencies are installed, you can start the project by running:
63
-
```bash
64
-
npm start
65
-
```
66
-
The project should now be running on your local machine. Open your web browser and navigate to http://localhost:3000 to view the project.
63
+
```bash
64
+
npm start
65
+
```
66
+
The project should now be running on your local machine. Open your web browser and navigate to http://localhost:3000 to view the project.
67
67
68
68
# How to open the PR
69
69
70
-
- If you're new to GitHub, here is a [tutorial describing Pull Requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
71
-
- create a branch
72
-
- branch better to be named after issue (or feature) it tries so solve, e.g. `feat/add-close-button-to-modal`
73
-
- Please make sure that the project works on your computer
74
-
- do changes and then - do commit (`git commit -m "feat: add some feature"`)
75
-
- push the branch to remote repo (`git push`)
76
-
- go to the repo and create a pr (by pressing `create a pr` button)
77
-
- tag one of the maintainers as reviewers
70
+
- If you're new to GitHub, here is a [tutorial describing Pull Requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request).
71
+
- create a branch
72
+
- branch better to be named after issue (or feature) it tries so solve, e.g. `feat/add-close-button-to-modal`
73
+
- Please make sure that the project works on your computer
74
+
- do changes and then - do commit (`git commit -m "feat: add some feature"`)
75
+
- push the branch to remote repo (`git push`)
76
+
- go to the repo and create a pr (by pressing `create a pr` button)
77
+
- tag one of the maintainers as reviewers
78
78
79
79
# Commit message convention
80
80
81
-
- commit messages better to be short and explain clearly what the change is about
82
-
- `fix` change that tries to fix some bug, e.g. `fix: make close button visible at mobile`
83
-
- `feat` change that add some new functionality, e.g. `feat: add a modal component`
84
-
- `docs` change that adds some documentation, e.g. `docs: add project description at readme`
85
-
- `refactor` change that makes the code better, e.g. `refactor: split App component to subcomponents`
86
-
- `chore` all the other things `chore: upgrade react package to new 18 version`
81
+
- commit messages better to be short and explain clearly what the change is about
82
+
-`fix` change that tries to fix some bug, e.g. `fix: make close button visible at mobile`
83
+
-`feat` change that add some new functionality, e.g. `feat: add a modal component`
84
+
-`docs` change that adds some documentation, e.g. `docs: add project description at readme`
85
+
-`refactor` change that makes the code better, e.g. `refactor: split App component to subcomponents`
86
+
-`chore` all the other things `chore: upgrade react package to new 18 version`
87
87
88
88
## testing the project:
89
89
@@ -97,35 +97,35 @@ Follow these steps to run the project on your local machine:
97
97
|`npm run test:e2e:ui`| Run the e2e (playwright) tests with user interface. |
- lint - you have lint errors. fix them by running `npm run lint:fix`
148
-
- tests - you have test errors. see them by running `npm run test:unit:ci`
149
-
- build - you have build errors. see them by running `npm run build`
150
-
- pr title validation - you have an invalid pr title. please edit the title of your PR with conventional commit formatting. examples: `feat: add new feature`, `fix: fix a bug` or `docs: update README.md`
147
+
- lint - you have lint errors. fix them by running `npm run lint:fix`
148
+
- tests - you have test errors. see them by running `npm run test:unit:ci`
149
+
- build - you have build errors. see them by running `npm run build`
150
+
- pr title validation - you have an invalid pr title. please edit the title of your PR with conventional commit formatting. examples: `feat: add new feature`, `fix: fix a bug` or `docs: update README.md`
Copy file name to clipboardExpand all lines: README.md
+24-15Lines changed: 24 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -1,61 +1,69 @@
1
1
# Open bus ranking app
2
2
3
3
## Welcome!
4
+
4
5
This is the official repository of the open bus (תחב"צ פתוחה / דאטאבוס) project - also known as "ShameBus".
5
6
[link to the project](https://open-bus-map-search.hasadna.org.il/dashboard)
6
7
7
8
Please feel free to submit pull requests and contribute to the project.
8
9
For more details about contributing, see the [CONTRIBUTING.md](CONTRIBUTING.md) file.
9
10
10
11
# Running the project locally
12
+
11
13
An explanation how to run the project locally you can [read here](CONTRIBUTING.md#running-the-project-on-a-local-environment).
12
14
13
15
## View video (Hebrew language):
14
-
### The video will explain you how to contribute to the project:
16
+
17
+
### The video will explain you how to contribute to the project:
18
+
15
19
[](https://www.youtube.com/watch?v=6H6jkJCVhgk)
16
20
17
21
# Easter eggs
22
+
18
23
We've hidden a couple of fun surprises in our web app, just for you. Discovering them is as easy as typing a few magic words on your keyboard.
19
24
20
25
## How to Find the Easter Eggs
26
+
21
27
1. Open our [web app](https://open-bus-map-search.hasadna.org.il/dashboard)
22
28
2.**Unleash the Magic Words:**
23
29
To reveal the hidden gems, use your keyboard to type the following commands:
24
-
25
30
-**Type "storybook":**
26
31
Watch the magic unfold as you type "storybook" on your keyboard. You might just stumble upon our Storybook, a treasure trove of UI components showcasing the beauty and functionality of our app.
27
32
-**Type "geek":**
28
33
To get some experimental charts with some additional data and aggregation
29
34
30
-
31
35
## deployments
32
36
33
37
This app is created by the volunteers of [Public Knowledge Workshop](https://www.hasadna.org.il/)
34
38
35
39
### submitting pull requests
40
+
36
41
Thanks for your willingness to invest time and help us improve!
42
+
37
43
1. If you're new to GitHub, here is a [tutorial describing Pull Requests](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request). if you're familiarized with Merge Requests - it's the same concept.
38
44
2. Please make sure that the project works on your computer
39
45
3. Please tag one of the maintainers as reviewers
40
-
we're here to help! feel free to join our [Slack channel](https://join.slack.com/t/hasadna/shared_invite/zt-21qipktl1-7yF4FYJVxAqXl0wE4DlMKQ)
46
+
we're here to help! feel free to join our [Slack channel](https://join.slack.com/t/hasadna/shared_invite/zt-21qipktl1-7yF4FYJVxAqXl0wE4DlMKQ)
0 commit comments