Skip to content

Conversation

@Daminou023
Copy link
Contributor

Commit Message Guidelines

Header
Blank Line
Body
Blank Line
Footer

The header should look like:
<type>(<scope>): <subject>

The body should have any necessary detailed info about the commit:
An example, references as to where this idea came from, etc.

The footer should have all the issues tagged:
Fixes #123, Fixes #456

So a commit should look like:
feat(users): Add new Yahoo authentication

Yahoo authentication idea proposed by @codydaig
Example implementation in file.js

Fixes #82
  • Types:
    • feat - Features, Enhancements, and overall Improvements
    • fix - Fixes, Bugs, HotFixs, etc...
    • doc - Changes to the Documentation and doesn't actually touch any code.
  • Scope:
    • The scope should be where the change took place.
    • Examples: users, core, config, articles
  • Subject:
    • The subject line should be clear and concise as to what is being accomplished in the commit.
  • General Rules:
    • No Line in the Commit message can be longer than 80 characters.
  • Reference: Angular Conventions

Daminou023 and others added 30 commits November 3, 2016 16:34
- Added a seperation between the admin view for the list of internships and the student view fot the list of
internships. The student can only see his own internships and the admin all of the internships.
Trum SAMAAAAA.
-Added the create internship form
-Modified the Internship model to reference Users
-Modified client route for create internship button
… coordinator view, Add fields to API requests & populates
…oded, approval statuses set to 'pending' when proposition created
…ment for coordinator. EDIT coordinator view, add supervisor choice from select of all teachers
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant