Should l have a reference to my commits, so I could rollback to it if i do a lot of works and get confused?

[azizamohamedabdelsalam]

While you described the hierarchy of commits and relations between them my question is Should l have a reference to my commits,?
So I could roll back to it if I do a lot of works and get confused.

[AhmedYousseff]

Hello Aziza Mohamed; if I may answer your question.
commit is a complete history of you application in specific time, so commit itself is a reference you could rollback to it at

        **DO NOT FORGET COMMIT ARE FOR FREE YOU CAN CREATE AS MUCH AS YOU LIKE** 

if you have a ticket that required a lot of work divide this ticket int multiple sub-ticket each sub-ticket is related to specific topic or problem, and after you finish this sub-ticket commit the benefit of doing
1 - you will not get confused
2- you will not have to rewrite a lot of code
one more thing git provide so many tools to use such as stashing, (detached HEAD could be useful in such scenario)
one more thing git reset is a destructive tool u should be aware of what it's doing to your area and to your repository

[azizamohamedabdelsalam]

Hello Aziza Mohamed; if I may answer your question.
commit is a complete history of you application in specific time, so commit itself is a reference you could rollback to it at

        **DO NOT FORGET COMMIT ARE FOR FREE YOU CAN CREATE AS MUCH AS YOU LIKE** 

if you have a ticket that required a lot of work divide this ticket int multiple sub-ticket each sub-ticket is related to specific topic or problem, and after you finish this sub-ticket commit the benefit of doing
1 - you will not get confused
2- you will not have to rewrite a lot of code
one more thing git provide so many tools to use such as stashing, (detached HEAD could be useful in such scenario)
one more thing git reset is a destructive tool u should be aware of what it's doing to your area and to your repository

Thank you , got it

[MohamedRadwan-DevOps]

@AhmedYousseff Thank you for your effort in answering this question, I do appreciate it!

[MohamedRadwan-DevOps]

@azizamohamedabdelsalam:
I have explained in the 2nd session the guidelines for questions or issues, please edit this issue and update it accordingly.

[MohamedRadwan-DevOps]

@azizamohamedabdelsalam another point, you can review the guidelines here #2

[MohamedRadwan-DevOps]

To answer this question, the answer is no, you should not do that, good comment for your commit should be enough.
Usually, you create this reference using tags, see how to do that in 2nd session by clicking here, also while I don't recommend creating tags without a major change like version but you still can do that in your feature branch and delete them before merging your branch to the master.