fvena

How to Work with Multiple GitHub Accounts on a Single Machine

This tutorial will guide you through setting up multiple GitHub accounts on the same machine. We'll use a personal account as the primary account and a work account as the secondary account.

Suppose you have two GitHub accounts:

• https://github.com/fvena-personal (personal - will be configured as primary)
• https://github.com/fvena-office (work - will be configured as secondary)

You can extend this logic to any number of accounts. The setup involves generating separate SSH keys, configuring your SSH client, and setting per‑repository user information.

fvena

🔄 Checking and Updating npm Packages

This is a quick rundown on how to check and update npm packages and package.json:

• npm outdated: Check for outdated packages.
• npm update --save: Update packages and save to package.json.
• npm update --save --save-dev: Update dependencies and devDependencies.
• npm update -g: Update global packages.

Alternatively, you can use npm-check-updates to check and update packages:

fvena

Add Git Branch Name to Terminal Prompt (zsh)

Theme

Install

1. Download the One Dark theme for Terminal
2. Double-click the scheme/terminal/One Dark.terminal. This will automatically open the Mac terminal with the One Dark theme applied temporarily.
3. To make it permanent, go to Terminal Preferences (⌘ + ,).

fvena

Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, gender, gender identity and expression, sex characteristics, disability, ethnicity, level of experience, education, socio-economic status, nationality, personal appearance, body size, race, religion (or lack thereof), or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

fvena

[Project Name]'s Guide to Git Commit Messages

This guide is an adaptation of Angular's commit convention.

Semantic commit messages follow a specific format to describe changes in a clear, structured, and consistent way. This helps developers and tools understand the purpose of each change and enables automated versioning systems like semantic-release.

General Commit Message Format

A commit message consists of a header, a body, and a footer.

fvena

⭐   to the project if you like it ↗️:

fvena

Contribuciones a [Nombre de tu Proyecto]

¡Gracias por tu interés en contribuir a [Nombre de tu Proyecto]! Este proyecto es un esfuerzo comunitario, y tu ayuda es esencial para su crecimiento y mejora.

Nuestra Visión

[Nombre de tu Proyecto] se dedica a [breve descripción del propósito y objetivos del proyecto]. Creemos firmemente en el poder del trabajo en equipo y en la mejora continua a través de las contribuciones de nuestra comunidad.

Compartiendo en Redes Sociales ❤️

fvena

Configuración global de Git

La configuración global de Git te permite establecer opciones personalizadas aplicables a todos los repositorios en tu sistema.

Configuración Básica

Establecer tu nombre y correo electrónico

Git utiliza estas credenciales para asociar tus commits con tu identidad.

fvena

Git Log Enhanced Visualization

These aliases create customized graphical views of the commit history, tailored for different needs and project types.

To simulate git history

git init example
cd example
git commit --allow-empty -m "initial empty commit"