Skip to content

Commit ac0f5c1

Browse files
committed
Update README
1 parent 9bdb08b commit ac0f5c1

File tree

1 file changed

+6
-4
lines changed

1 file changed

+6
-4
lines changed

README.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -62,9 +62,9 @@ The goal of this exercise is to get you used to the TDD flow.
6262

6363
We've provided you with appropriate tests to guide and validate your solution. You need to make all the tests pass, one by one, by implementing the `load` method in the existing `RemoteFeedLoader` class.
6464

65-
1) Fork the latest version of the challenge repo.
65+
1) Fork the latest version of the challenge repo. Here's <a href="https://guides.github.com/activities/forking" target="_blank">how forking works</a>.
6666

67-
2) Open the `FeedAPIChallenge.xcodeproj` project.
67+
2) Open the `FeedAPIChallenge.xcodeproj` project on Xcode 12.
6868

6969
3) There are two main folders in the project:
7070
- The `FeedAPIChallenge` folder contains the production types, including the `RemoteFeedLoader` and dependencies for requesting and loading the feed remotely. ***You only need to change the `RemoteFeedLoader.swift` file to implement the `load` method.***
@@ -75,7 +75,9 @@ We've provided you with appropriate tests to guide and validate your solution. Y
7575

7676
5) While developing your solutions, run all tests with CMD+U.
7777

78-
6) When all tests are passing and you're done implementing your solution, create a Pull Request from your branch to the main challenge repo.
78+
6) When all tests are passing and you're done implementing your solution, create a Pull Request from your branch to the main challenge repo **with the title: "Your Name - Feed API Challenge**.
79+
80+
**7) Post a comment in the challenge page in the academy with the link to your PR, so we can review your solution and provide feedback.**
7981

8082

8183
## Guidelines
@@ -94,4 +96,4 @@ We've provided you with appropriate tests to guide and validate your solution. Y
9496

9597
7) Aim to write self-documenting code by providing context and detail when naming your components, avoiding explanations in comments.
9698

97-
8) Strive to produce a clean solution as it can be **an ideal addition to your project portfolio**!
99+
Happy coding!

0 commit comments

Comments
 (0)