cecileane
commented
3 years ago 🎉
just a quick note Ashvini: if you add a space between @ and someone's GitHub name, like @ cecileane, then the tag doesn't work. there shouldn't be a space, like @cecileane. You can double-check by clicking on "Preview" before submitting a comment. If the preview shows the tab in bold, then it worked --and the name didn't have a typo. I always check, because I often make typos! If the tag is not in bold (like in your comment above), then there's an issue (typo, or space above).
Nice readme! 👍
A few more things:
- your merge was not clean: you left some marks showing where the conflict started: see e11ed17b598fa with the marks
<<<<<<< HEADshowing the start of the conflict, and=======showing the middle of the conflict. You eliminated the start mark<<<<<<< HEADin the next commit: 7331d9f56587 but you left in the middle mark=======. Just so you know if you run into an unexpected git conflict some day! - html syntax should be avoided in markdown. For instance, you should avoid
<p> </p>or<br>. If you want to force more blank space, you have several options:- add 2 spaces at the end of a line: this forces a newline (like
<br>would do in html) - use headers: those will create more space around
- use more lists: those will force more space before & after.
- add 2 spaces at the end of a line: this forces a newline (like
AshviniFulpagar
Course Notes: I have created a Stat679_CourseNotes directory.
I will be adding other course notes and projects here in the coming week.
What I have learned so far: @cecileane and @tzuhsianghung I would like to say thank you for the many things I have learned in this course. I learned how to organize the Project, project-related files and directories and how to name those things. I have started using these guidelines and naming conventions in other courses, homework, projects, and in my hard-drive as well which has absolutely made my life easier!
To Do: Add remaining notes of this course before 2020/10/06