IEEEXtreme

Solutions to IEEEXtreme problems

File Structure

• Full solutions are named as solution.{extension}
• Partial solutions are named as solution.partial.{extension}

Commit Guidelines

Goals

• provide better information when browsing the history

Format of the commit message

<type>(<scope>): <subject>

Any line of the commit message cannot be longer 100 characters! This allows the message to be easier to read on github as well as in various git tools.

Allowed <type>

• feat (feature)
• fix (bug fix)
• docs (documentation)
• style (formatting, missing semi colons, …)
• refactor
• test (when adding missing tests)
• chore (maintain)

Allowed <scope>

Scope could be anything specifying place of the commit change. For example $location, $browser, $compile, $rootScope, ngHref, ngClick, ngView, etc...

<subject> text

• use imperative, present tense: “change” not “changed” nor “changes”
• don't capitalize first letter
• no dot (.) at the end

Commit guidelines obtained from

https://gist.github.com/stephenparish/9941e89d80e2bc58a153