# Section 3 - Browsing History: Lesson 16 - Using GitLens

**URL:** <https://forum.codewithmosh.com/t/section-3-browsing-history-lesson-16-using-gitlens/7032>\
**Category:** Git\
**Created:** [August 27, 2021, 7:18pm UTC](https://forum.codewithmosh.com/t/section-3-browsing-history-lesson-16-using-gitlens/7032 "2021-08-27T19:18:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![JosephGarza](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.codewithmosh.com/josephgarza/32/2195_2.png) [@JosephGarza](https://forum.codewithmosh.com/u/JosephGarza)\
**Post date:** [August 27, 2021, 7:18pm UTC](https://forum.codewithmosh.com/t/section-3-browsing-history-lesson-16-using-gitlens/7032/1 "2021-08-27T19:18:13Z")

</div>

Greetings and Salutations to all! I would like to know if I could please draw someone’s attention to this confusion I have. I am working in Section 3 - Browsing History, doing lesson 16 - Using GitLens in VSCode but how is it that I am supposed to access the history of the file that we are working on?

NOTE - We are asked to download the zip file named “Venus” and to save it in our device. BUT, I never noticed any instructions that lead us to clone a repository that contained previous commits.

QUESTION - Did anyone see those instructions in previous lectures in section 3 from lessons 2 to 15?

When I get to lesson 16, and I search for these commits using GitLens, I get nothing. Is this just to show what we can do with GitLens or is there something I am missing?

SoS anyone, please.

---

<div class="post-metadata">

**Author:** ![jmrunkle](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.codewithmosh.com/jmrunkle/32/3765_2.png) [@jmrunkle](https://forum.codewithmosh.com/u/jmrunkle)\
**Post date:** [August 7, 2022, 3:57am UTC](https://forum.codewithmosh.com/t/section-3-browsing-history-lesson-16-using-gitlens/7032/2 "2022-08-07T03:57:44Z")

</div>

Not much detail to go on, but perhaps the copied file permissions did not get setup correctly? In particular you probably care about the file permissions on the `.git` directory. Depending on how you extract the files it is possible to accidentally end up with read-only stuff rather than having write access to things (and Git definitely needs write access to that `.git` directory). If you are using MacOS or any Linux/Unix OS you can use `chmod +w` to add the write permissions.