Skip to content

Instantly share code, notes, and snippets.

View ibakshay's full-sized avatar

Akshay Iyyadurai Balasundaram ibakshay

  • St Leon-Rot
  • 20:32 (UTC +02:00)
View GitHub Profile
@hackjutsu
hackjutsu / upstream.md
Last active December 11, 2023 07:44
[set upstream] What does '--set-upstream' do? #tags: git
git branch --set-upstream-to <remote-branch>
# example
git branch --set-upstream-to origin feature-branch

# show up which remote branch a local branch is tracking
git branch -vv

sets the default remote branch for the current local branch.

@bradtraversy
bradtraversy / myscript.sh
Last active April 22, 2025 23:48
Basic Shell Scripting
#! /bin/bash
# ECHO COMMAND
# echo Hello World!
# VARIABLES
# Uppercase by convention
# Letters, numbers, underscores
NAME="Bob"
# echo "My name is $NAME"
@jamezrin
jamezrin / orphan.py
Last active June 25, 2022 13:34
Python script to create an orphan branch
import requests
def create_orphan_branch(repository, authentication, branch_name,
github_api_path='https://api.github.com'):
res1 = requests.get(
github_api_path + '/repos/{0}/{1}/git/refs/heads/{2}'.format(
repository['owner'],
repository['name'],
branch_name
@bradtraversy
bradtraversy / mysql_cheat_sheet.md
Last active April 26, 2025 21:23
MySQL Cheat Sheet

MySQL Cheat Sheet

Help with SQL commands to interact with a MySQL database

MySQL Locations

  • Mac /usr/local/mysql/bin
  • Windows /Program Files/MySQL/MySQL version/bin
  • Xampp /xampp/mysql/bin

Add mysql to your PATH

@ReeganExE
ReeganExE / post-json.go
Created February 15, 2020 08:00
Sample POST json in Go
package main
import (
"bytes"
"encoding/json"
"fmt"
"io"
"log"
"net/http"
"os"
@firxworx
firxworx / app.e2e-spec.ts
Created June 29, 2020 16:24
NestJS Integration/E2E Testing Example with TypeORM, Postgres, JWT
import { Test, TestingModule } from '@nestjs/testing'
import { INestApplication, LoggerService } from '@nestjs/common'
import * as request from 'supertest'
import { AppModule } from './../src/app.module'
class TestLogger implements LoggerService {
log(message: string) {}
error(message: string, trace: string) {}
warn(message: string) {}
debug(message: string) {}
#########################################################
# Tekton #
# Kubernetes Cloud-Native CI/CD Pipelines And Workflows #
# https://youtu.be/7mvrpxz_BfE #
#########################################################
# Referenced videos:
# - Argo Workflows and Pipelines - CI/CD, Machine Learning, and Other Kubernetes Workflows: https://youtu.be/UMaivwrAyTA
# - Automation of Everything - How To Combine Argo Events, Workflows & Pipelines, CD, and Rollouts: https://youtu.be/XNXJtxkUKeY
# - Kaniko - Building Container Images In Kubernetes Without Docker: https://youtu.be/EgwVQN6GNJg
@okineadev
okineadev / commit-message-guidelines.md
Last active April 28, 2025 17:42
🤖 Copilot commit messages instructions for VS Code

Paste it to settings.json:

"github.copilot.chat.commitMessageGeneration.instructions": [
  {
    "text": "Follow the Conventional Commits format strictly for commit messages. Use the structure below:\n\n```\n<type>[optional scope]: <gitmoji> <description>\n\n[optional body]\n```\n\nGuidelines:\n\n1. **Type and Scope**: Choose an appropriate type (e.g., `feat`, `fix`) and optional scope to describe the affected module or feature.\n\n2. **Gitmoji**: Include a relevant `gitmoji` that best represents the nature of the change.\n\n3. **Description**: Write a concise, informative description in the header; use backticks if referencing code or specific terms.\n\n4. **Body**: For additional details, use a well-structured body section:\n   - Use bullet points (`*`) for clarity.\n   - Clearly describe the motivation, context, or technical details behind the change, if applicable.\n\nCommit messages should be clear, informative, and professional, aiding readability and project tracking."
  }
]