Closed TraceLarson closed 6 years ago
Trace,
I'm noticing with your commits that your messages don't always match up with what is being committed. For example, your "Updated README.md with some instructions on how to run the project..." also contains work done for another purpose. Get in the habit of committing only work that matches the current issue, feature, bug, or enhancement. This will help in future debugging and in the worst case, code base roll-backs that can be more finely pin-pointed.
Expand on your .gitignore
file further. You'll want to block items such as a /node_modules
directory or .env
files within there. Github offers some pretty great templates based on the language of the repo, you may want to start there. Also, many open-source projects and starter templates ship with great .gitignore
examples. Look there as well.
You look to be carrying good momentum on the production side of this project. Keep up the strong efforts!
Commits: b55c96e 13f510d 10f5f6f 2206178
address pull request issues.
Reworked branches to have a central Dev branch with the Dev-Back-End branch to be merged into main Dev branch.