Based on Week 10 tasks, //@@author [github user] should be used sparingly because its effects extend until another //@@author [github user] annotation is found or the end of the file is reached.
Moving forward, we should strive to "close" our //@@author [github user] annotations such that we don't inadvertently claim more code than intended.
Also, a lesson learnt is that syncing a updated upstream master with a local development branch (with conflicts there were resolved) messes with the native GitHub log system and incorrectly attributes all merged code as authored by the developer who synced. Try to limit this for now.
Based on Week 10 tasks,
//@@author [github user]should be used sparingly because its effects extend until another//@@author [github user]annotation is found or the end of the file is reached.Moving forward, we should strive to "close" our
//@@author [github user]annotations such that we don't inadvertently claim more code than intended.Also, a lesson learnt is that syncing a updated upstream master with a local development branch (with conflicts there were resolved) messes with the native GitHub log system and incorrectly attributes all merged code as authored by the developer who synced. Try to limit this for now.