Lesson 7: Pushing to github

[codeplay22]

i have just pushed my code once and it's shows 3 commit's why?

[EngrPips]

I assume the push action and the commit action are not the same. The commit action commits changes to git, while the push action pushes code to GitHub. So, I will say that makes sense.

[thebraveman17]

As much as I know, Foundry automatically creates a commit on initialization of a new project and on adding a new dependency so that's two commits. Even though forge-std is a built in library, I guess it is still counted as a dependency. The third commit is the one you made before pushing to GitHub I guess.

If you remember, Patrick said in the course to always add "--no-commit" when installing a dependency. That's exactly because of the default behavior of Foundry to create a commit after installing a dependency so you have to instruct it not to create a new commit.

[EngrPips]

Indeed

[codeplay22]

Hi @thebraveman17
Thanks a lot for you answer! Now i understood why we write --no-commit with every dependency we install.
So if i write forge init --no-commit then it will not count as a commit, right?

[EngrPips]

Yeah i believe

[thebraveman17]

@codeplay22 That's right, you can use --no-commit to instruct Foundry not to create a commit.

On the first picture you can see the git log (commits) after creating a new project using forge init. As you can see, there are two commits as I explained above.

On the second picture you can see the output of git log after creating a new project using forge init --no-commit. As you can see, there are no commits.

[codeplay22]

@thebraveman17 Thanks!