Skip to content

Commit e1c4cd3

Browse files
authored
docs: updates PR requirements for teammates (#678)
1 parent 94d036f commit e1c4cd3

File tree

1 file changed

+5
-1
lines changed

1 file changed

+5
-1
lines changed

capstone/README.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,12 +2,16 @@
22

33
For the next two weeks, you and your team will ideate and implement a working software system. You will have the opportunity to apply the skills that you have learned to solve an interesting problem or contribute a meaningful tool that improves our lives.
44

5+
### Changelog
6+
- 12/4 @anthonydmays Updated technical requirement for number of PRs submitted per teammate.
7+
- 12/2 @anthonydmays Published initial version
8+
59
### Technical Requirements
610

711
Your project submission must include the following elements:
812

913
* All work must be submitted in your team's assigned GitHub repository. Your team must track issues, bugs, pull requests, and features. See [Lesson 05][lesson-05] for a refresh.
10-
* Each team member must contribute *at least one* submitted pull request containing working code and tests. See [Lesson 15][lesson-15] for a refresh.
14+
* Each team member must contribute *at least two* submitted pull requests containing working code and tests. See [Lesson 15][lesson-15] for a refresh.
1115
* Write unit tests achieving 70% code coverage (using JaCoCo for Java or Jest for Typescript).
1216
* Must have a working front-end that interacts with a back-end web service to retrieve and persist data.
1317
* Your app must be publicly accessible. It is recommended that you use [Vercel](https://vercel.com) or [Fly.io](https://fly.io) to deploy your apps.

0 commit comments

Comments
 (0)