updating markdown doc on folder "projects"

IALSA / ialsa-2015-portland-stencil

Applying lessons from the Feb 2015 Portland workshop to a newer architecture

GNU General Public License v2.0

0 stars 0 forks source link

updating markdown doc on folder "projects" #11

Closed Maleeha closed 8 years ago

Maleeha commented 8 years ago

@wibeasley
Please note, i have a few questions about this folder that i will ask tomorrow. For now the folder and its contents have been updated in the markdown document. repo-files.md < https://github.com/IALSA/ialsa-2015-portland-stencil/commit/908591c6cdb3ec16b87802f16117ee61ddb7ef3e>

wibeasley commented 8 years ago

I'll jot a few things to help me remember. I'll probably edit this one post several times as I see things.

Peculiars of folder "projects"is a huge commit of 50 files. Try to keep the commits small enough that you could wrap your brain around each one individually. If a single commit requires 2 hours, it might be a sign that it should have been separated into smaller commits.
Don't bother including the dates in the commit messages. Think of them kinda like book or article titles.

Maleeha commented 8 years ago

@wibeasley,

[x] Got the not dating the commits part.
[ ] What did you mean by keep the commits small? Because when I am constructing from the scratch, I can keep them small, But Dr. Beasely, in this particular instant, I am directly coping them from IALSA folder to the stencil. I open the documents or files to look what they are so I can do my markdown description. Do I continue the way I have been doing this or just start committing slowly over a period of time.

wibeasley commented 8 years ago

Instead of a single big commit of 50 files spanning ~10 different directories, consider if it's conceptually cleaner to make 5 commits of 10 files each (group the commits by directory).

This isn't an absolute rule. Just consider if the commits would have been more coherent. Maybe not.