Skip to content

Commit b8d9afc

Browse files
authored
Merge pull request #2435 from ironhack-labs/uros/feat/add-faqs-section
minor style updates
2 parents c033b32 + 2846a32 commit b8d9afc

File tree

1 file changed

+5
-8
lines changed

1 file changed

+5
-8
lines changed

README.md

Lines changed: 5 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -293,20 +293,17 @@ __Happy coding!__ :heart:
293293
There are a couple of possible reasons why you may be unable to *push* changes to a Git repository:
294294
295295
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:
296-
297-
```bash
298-
git add .
299-
git commit -m "Your commit message"
300-
git push
301-
```
296+
```bash
297+
git add .
298+
git commit -m "Your commit message"
299+
git push
300+
```
302301
303302
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.
304303
To check which remote repository you have cloned, run the following terminal command from the project folder:
305-
306304
```bash
307305
git remote -v
308306
```
309-
310307
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.
311308
312309
Note: You may want to make a copy of the code you have locally, to avoid losing it in the process.

0 commit comments

Comments
 (0)