Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Production release v24.11.0 #7387

Merged
merged 8 commits into from
Mar 11, 2024
Prev Previous commit
Next Next commit
Improve contributing guidelines in README (#7370)
* Improve contributing guidelines in README

* Update README.md

* specify issue number in branch name
rithviknishad authored Mar 11, 2024
commit 540f45ada501a8c6805674fbffee2224943ebfb7
10 changes: 6 additions & 4 deletions README.md
Original file line number Diff line number Diff line change
@@ -63,11 +63,13 @@ Authenticate to staging API with any of the following credentials
role: Doctor
```

#### 🏷️ Make use labels to update the PR/issue status
#### Contributing to CARE

- Mark your PRs as `work-in-progress` if it's still being worked on.
- Once you have solved the related issue, mark your PR with `need testing` and `need review` labels.
- When you’re making a PR with lots of code changes that affects multiple functionalities, or is likely to break, make sure you tag it with `Major Code Change` label.
- Create a branch with branch name of the format `issues/{issue#}/{short-name}` (example `issues/7001/edit-prescriptions`) from the latest [`develop`](https://github.com/coronasafe/care_fe/tree/develop) branch when starting to work on an issue.
- Once the changes are pushed to the branch, make a pull request with a meaningful title (example: "💊 Adds support for editing prescriptions" #6369)
- Ensure the issue number is mentioned in the PR with a closing tag by following the PR body template. (Refer: [Linking a pull request to an issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))
- Once the code review is done, the PR will be marked with a "Needs Testing" label where it'll be queued for QA testing.
- Once tested, the PR would be marked with a "Tested" label and would be queued for merge.

#### 🧪 Run cypress tests