A software engineer interested in solving real problems, developer productivity & learning languages for fun. Primarily working on Node.js, React & databases. Current Interest: Rustlang
Definitely true with the bunch of config files during in the for of the repo.
I normally see these list
Package.json
Yarn.lock/package-lock.json
Prettier and / or editorconfig
Gitlab ci/ circle CI / GitHub workflows config etc
Makefile or setup if if requires some custom config.
So they all make the barrier of entry a little higher. Probably we could create a single to level file that shares a link to all the config files which are in another sub directory. It doesn't help much but keeps the repository beginner friendly.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Definitely true with the bunch of config files during in the for of the repo.
I normally see these list
So they all make the barrier of entry a little higher. Probably we could create a single to level file that shares a link to all the config files which are in another sub directory. It doesn't help much but keeps the repository beginner friendly.