vscode-seneca-college VS tokens

2) vscode Extension for Seneca 🧩

I also ended up doing a last-minute contribution to vscode-seneca-college extension repo for the issue regarding displaying user stats such as screen time and edits made per hour.

Seneca-CDOT has many amazing open-source projects to which students are actively contributing - telescope, my-photohub, vscode-extension, and so on - and from those options, I chose to work on My Photohub as I found the idea of storing a picture on a GitHub repo very innovative. It was also a new project and I wanted to be among the first time contributors.

This week I was working on my school's vs code extension which is open-sourced and hosted on the github.

As a part of my release 0.3 for OSD600, I had to create 2 code reviews for internal Seneca College open-source projects. Both of my code reviews were for vscode-seneca-college.

Issue 7

I also did a code review in vs-code-seneca-college extension in development, which aims to make collaboration for developers at Seneca College easier.

Second review

Link: https://github.com/Seneca-CDOT/vscode-seneca-college/pull/13

The projects I chose were Intro2C which is a beginner's course into C programming, and vscode-seneca-college, which is a VS Code extension for Seneca students.

Click on your profile in the top right corner > Settings > Developer settings, or visit: https://github.com/settings/tokens.

First of all, you need to generate a new GitHub Token. You can generate a token in your GitHub account settings at https://github.com/settings/tokens. Make sure to add the ‘read:packages’ scope to your token.

First, generate the GitHub token here.

Environment Variables Create a file .env in the root folder and add your own github api token as below

Go to the Personal access tokens area in the Developer settings of your GitHub profile and click Generate new token.

Versioning The initial step in this workflow involves generating version numbers based on git tag numbers. To access repository information, it's necessary to include a GitHub token in the secrets. You can create a GitHub token by following this link. Please keep in mind that secret names cannot start with the term GITHUB. For instance, you might save your GitHub token as TOKEN_GITHUB.

GitHub has tucked the personal access tokens admin in a slightly hard-to-find location. From anywhere in GitHub, you can click on your profile image → Settings → Developer Settings → Personal Access Tokens.

Generate a classic PAT (personal access token) from Github with repo and admin:org scopes at least.

YOUR_TOKEN="no_token_for_you" # IMPORTANT: your Github API access key, make one at "https://github.com/settings/tokens"

You should click on that and then you will see Tokens (classic) which will bring you to https://github.com/settings/tokens