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
👍🎉 First off, congrats on getting put on this pod 😂🎉👍
3
4
4
5
The following is a set of guidelines for contributing to our backend. These are mostly guidelines, not rules. Use your best judgment, and feel free to propose changes to this document in a pull request.
5
6
6
7
# Versioning
8
+
7
9
This is _extremely_ important as handling our backend can get quite messy.
8
10
9
11
# Making PRs
12
+
10
13
We want our PRs to be concise but informative. Some pointers as per our PR template:
14
+
11
15
### Title
16
+
12
17
Summarize what changes you've made in one sentence. For example: "Exclude staff from the check for follows". For stacked PRs, please indicate clearly in the title where in the stack you are. For example: "[Eatery Refactor][4/5] Converted all files to MVP model."
18
+
13
19
### Overview
20
+
14
21
Summarize generally what the purpose of this PR is.
22
+
15
23
### Changes
24
+
16
25
Include details of what your changes actually are and how it is intended to work.
26
+
17
27
### Test Coverage
28
+
18
29
Describe how you tested this feature: manual testing and/or unit testing. Please include repro steps and/or how to turn the feature on if applicable. In the context of this repo, add a plan for how you intend to test on [integration](https://github.com/cuappdev/integration), with your newly created issue linked.
30
+
19
31
### Next Steps
32
+
20
33
If this applies, describe how you plan on addressing future PRs if this is a part of a multi-PR change.
34
+
21
35
### Related PRs or Issues
22
-
If this applies, list related PRs against other branches or repositories.
23
36
37
+
If this applies, list related PRs against other branches or repositories.
0 commit comments