Skip to content

Summer students 2019' intro to Angular

Notifications You must be signed in to change notification settings

Dualog-students/Neptun

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

67 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation


Logo

Neptun

An introduction to Angular project for the summer students at Dualog

Usage

Development

Run ng serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Build

Run ng build to build the project. The build artifacts will be stored in the dist/ directory. Use the --prod flag for a production build.

Coding conventions

Commit naming

All Git Commit Messages should meet the following text format:

Subject line
(One newline)
Message Body
(One newline)
Ref <###>

Rules

  1. Capitalize the Subject.
  2. Do not end the Subject line with a period.
  3. Message Body should end with at least one issue tracking reference.
  4. Use valid MarkDown in the message body.
  5. Use the present tense ("Add feature" not "Added feature").
  6. Use the imperative mood ("Move cursor to..." not "Moves cursor to...").
  7. Use the message body to explain what and why vs. how.

Branch naming

Naming When to use?
feature/awesome-branch-name When developing a new feature
bugfix/awesome-branch-name When fixing a bug
hotfix/awesome-branch-name When fixing an urgent bug
docs/awesome-branch-name When updating documentation
tooling/awesome-branch-name When changing tooling
performance/awesome-branch-name When improving performance
refactoring/awesome-branch-name When refactoring code
cosmetic/awesome-branch-name When improving UI/Cosmetic
testing/awesomest-branch-name When adding tests