BioSTEAMDevelopmentGroup / BioSTEAMDevelopmentGroup/biosteam-web

Access/fork setting, could not run locally

Open
#2 9 comments 0 reactions 0 assignees View on GitHub
Dominant language
Vue
Stars
3
Forks
0
PR merge metrics
No merged PRs in 30d

Description

OK I'm having several problems here:

1. Not sure if this is my problem with the setting, but do I have writing access to this repo @kgukevin @yoelcortes ? I made some changes and tried to push, but git refused (and docs [here](https://docs.github.com/en/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors#error-repository-not-found) said it could be I didn't have the permission)
Screen Shot 2021-11-24 at 9 47 58 AM

2. Also forking is disabled so I couldn't fork as well. Why would we want this repo to be private?

3. Additionally, I couldn't run it locally, the error screenshot/log are attached

Screen Shot 2021-11-24 at 9 51 15 AM

[eresolve-report.txt](https://github.com/BioSTEAMDevelopmentGroup/biosteam-web/files/7597035/eresolve-report.txt)

4. Why `package.json` is included in `.gitignore`? I thought we would want the dependencies info to be up to date, including `package-lock.json` in `.gitignore` makes sense because that'll be generated locally when running `npm install`
- related, we should probably remove the existing `package-lock.json` file?

Thanks!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.