Skip to content

Instantly share code, notes, and snippets.

View TangoPJ's full-sized avatar
🎯
Focusing

Rail Batyrshin TangoPJ

🎯
Focusing
  • Kyrgyzstan
View GitHub Profile
import Link from 'next/link'
import styles from './GithubRender.module.css'
import Fork from '../../images/fork.svg'
import Star from '../../images/star.svg'
import Image from 'next/image'
import { getInfoFromGit } from '../../api'
import { useEffect, useState } from 'react'
export const GithubRender = () => {
const [repos, setRepos] = useState([])
@leo-pfeiffer
leo-pfeiffer / pomodoro.sh
Last active May 7, 2024 12:41
Pomodoro timer for the (Mac OS) terminal
#!/bin/bash
set -eu
# sourceable pomodoro command
pomodoro() {
# print help
echo_help() {
# Display help
echo "Pomodoro timer for the terminal."
@tyomo4ka
tyomo4ka / git-aliases.md
Last active March 19, 2024 22:10 — forked from mwhite/git-aliases.md
The Ultimate Git Alias Setup on OS X (brew)

The Ultimate Git Alias Setup on OS X (brew)

If you use git on the command-line, you'll eventually find yourself wanting aliases for your most commonly-used commands. It's incredibly useful to be able to explore your repos with only a few keystrokes that eventually get hardcoded into muscle memory.

Some people don't add aliases because they don't want to have to adjust to not having them on a remote server. Personally, I find that having aliases doesn't mean I that forget the underlying commands, and aliases provide such a massive improvement to my workflow that it would be crazy not to have them.

The simplest way to add an alias for a specific git command is to use a standard bash alias.

# .bash_profile