//server/controllers/_ticket-control.js | |
'use strict'; | |
const Tickets = require('../models/tickets'); | |
//=================== | |
// Create Tickets Route | |
//=================== | |
exports.createTicket = function(req, res, next) { |
Do you need a refresher on git? Go through Codecademy's git
course.
-
Using your terminal/command line, get inside the folder where your project files are kept:
cd /path/to/my/codebase
. → You cannot do this simply by opening the folder normally, you must do this with the command line/terminal.
→ Do you need a refresher on using your command line/terminal? I've compiled my favorite resources here. -
Check if git is already initialized:
git status
A commit should be a wrapper for related changes. For example, fixing two different bugs should produce two separate commits. Small commits make it easier for other developers to understand the changes and roll them back if something went wrong. With tools like the staging area and the ability to stage only parts of a file, Git makes it easy to create very granular commits.
Committing often keeps your commits small and, again, helps you commit only related changes. Moreover, it allows you to share your code more frequently with others. That way it‘s easier for everyone to integrate changes regularly and avoid having merge conflicts. Having large commits and sharing them infrequently, in contrast, makes it hard to solve conflicts.