Skip to content

Commit aa7ac24

Browse files
authored
remove unnecessary repeated q in faq
1 parent 2d06cee commit aa7ac24

File tree

1 file changed

+0
-29
lines changed

1 file changed

+0
-29
lines changed

README.md

Lines changed: 0 additions & 29 deletions
Original file line numberDiff line numberDiff line change
@@ -353,35 +353,6 @@ Following the logic you've used in iteration #8.1, declare a function called `gr
353353

354354
</details>
355355

356-
<details>
357-
<summary>I am unable to push changes to the repository. What should I do?</summary>
358-
<br>
359-
360-
There are a couple of possible reasons why you may be unable to *push* changes to a Git repository:
361-
362-
1. **You have not committed your changes:** Before you can push your changes to the repository, you need to commit them using the `git commit` command. Make sure you have committed your changes and try pushing again. To do this, run the following terminal commands from the project folder:
363-
364-
```bash
365-
git add .
366-
git commit -m "Your commit message"
367-
git push
368-
```
369-
370-
371-
2. **You do not have permission to push to the repository:** If you have cloned the repository directly from the main Ironhack repository without making a *Fork* first, you do not have write access to the repository.
372-
To check which remote repository you have cloned, run the following terminal command from the project folder:
373-
374-
```bash
375-
git remote -v
376-
```
377-
378-
If the link shown is the same as the main Ironhack repository, you will need to fork the repository to your GitHub account first, and then clone your fork to your local machine to be able to push the changes.
379-
380-
Note: You may want to make a copy of the code you have locally, to avoid losing it in the process.
381-
382-
[Back to top](#faqs)
383-
</details>
384-
385356
<details>
386357
<summary>All of the Jasmine tests are failing and in red. Why did this happen?</summary>
387358
<br>

0 commit comments

Comments
 (0)