Skip to content

Latest commit

 

History

History
69 lines (44 loc) · 3.11 KB

README.md

File metadata and controls

69 lines (44 loc) · 3.11 KB
Raw

Issue and Bug Tracker

GitHub Actions CI CodeQL codecov

Description

Open Source Issue and Bug Tracker written in Angular and Firebase

Website

issuetracker.dinodev.hu

Open Source Issue and Bug Tracker written in Angular and Firebase

Development

Prerequisites

Install Git, the free and open source distributed version control system.
Install Node.js which includes Node Package Manager.

Clone and Install

Run npm install -g @angular/cli to install the Angular CLI globally
Run git clone [email protected]:orbanszlrd/issuetracker.dinodev.hu.git to clone the repository from GitHub.
Run git clone [email protected]:orbanszlrd/issuetracker.dinodev.hu.git to clone the repository from GitLab.
Run git clone [email protected]:orbanszlrd/issuetracker.dinodev.hu.git to clone the repository from Bitbucket.
Run npm install or npm ci to install the dependencies.

Development server

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.

Code scaffolding

Run ng generate component component-name to generate a new component. You can also use ng generate directive|pipe|service|class|guard|interface|enum|module.

Build

Run ng build or npm run build:prod to build the project. The build artifacts will be stored in the dist/ directory.

Running unit tests

Run ng test, npm run test:ci, npm run test:github, npm run test:coverage or npm run test:codecov, to execute the unit tests via Karma.

Running end-to-end tests

Run ng e2e or npm run cypress:run to execute the end-to-end tests.

Further help

To get more help on the Angular CLI use ng help or go check out the Angular CLI Overview and Command Reference page.

Contributing

  • Fork the project repository
  • Clone your fork
  • Navigate to your local repository
  • Check that your fork is the "origin" remote
  • Add the project repository as the "upstream" remote
  • Pull the latest changes from upstream into your local repository
  • Create a new branch
  • Make changes in your local repository
  • Commit your changes
  • Push your changes to your fork
  • Begin the pull request
  • Create the pull request