ashutosh1919
Add .env to the Project For Github Token
This PR removes the GitHub token and username from the git_data_fetcher.mjs and adds it to a new env file.
Changes
- Added an env.example file with token and username which users will have to rename to .env.
- Added new instructions in README.
- Added dotenv package as a dev dependency as it is needed to use .env variables.
- Added .env to gitignore.
This PR addresses #220
@ashutosh1919 do have a look!
Yes @ashutosh1919 not yet able to understand why is the build failing. Will figure it out and update
@saiteja13427 Also we need to figure out a way to remove the package-lock.json file from the repo. Everytime we update a package, it shows huge change in that file.
@saiteja13427 & @ashutosh1919 someone with the privileges need to retrigger the builds from GitHub actions. This issue occurs if there are simultaneous PRs and the build is going on simultaneously.
@tamojit-123 I have actually tried running the test again back then but that did not work out actually. Will check this again and see.
Please refer to this link might help: https://stackoverflow.com/questions/68021121/fsevents-not-accessible-from-jest-haste-map I did it the same way or else Update your branch through this PR : https://github.com/ashutosh1919/masterPortfolio/pull/254
@tamojit-123 The issue was an incompatibility of the dotenv version actually, I resolved it.
So, I am closing #254
@ashutosh1919 Do have a look at this PR
Will merge it once you have a look.
We will have to update our testing npm versions and lock file versions to do updates to packages in future. We can also change our tests from node 10.x 12.x to 14.x and 16.x maybe.