IYC FRAMEWORK
IYC FRAMEWORK with boostrap version 5
Installation
npm install
Branches
As a general rule, each feature should be implemented on its own branch.
Notice: When working on branches that other devs might also be working on (this of course includes all special branches mentioned below),
- push your changes to the branch as soon as is sensibly possible
- don't merge from your own copy of the branch, but from the shared one (i.e., use
git pull origin <branch>
instead ofgit merge <branch>
)
Changes ready to be tested can be merged into the randi
branch. For example,
git commit -m "Finish new great feature"
git push origin great-feature
git checkout randi
git pull origin randi
git pull origin great-feature
git push origin randi
After successful testing, changes should be merged into master
.
Do not merge from randi
into any other branch, since it might contain draft changes!
The branch that contains deployed code is master
.
New features should thus normally start from master
(unless there is a specific reason to do otherwise).
Reminder: Make sure to delete your branches when they are no longer needed!
Run the project
npm run start
Build the project
npm run build