okineadev

import smtplib
from email.mime.text import MIMEText
from typing import List

def send_email(
    smtp_server: str,
    smtp_port: int,
    email: str,
    password: str,
    recipients: List[str],

okineadev

Hi, I had this problem today - I had an old repository from when I was just starting to work with Git, and I needed to hide the change history because there was information in a certain commit that I didn't want to disclose.

But I have a lot of commits there, and I don't want to lose my beloved commit statistics, so how do I solve this? 🤔

To do this, we need to edit all commits in the repository and hide the changes and change commit names to [REDACTED]

Here is the script for that 👇

# Save the current commit hash to a variable so we can go back to it later

okineadev

# 📰 https://web.archive.org/web/20210513172249/hackershark.com/2021/05/13/how-to-ssh-into-your-chromebook-through-linux-beta/

# 1. 🔓 Unlock the SSH server
sudo rm /etc/ssh/sshd_not_to_be_run

# 2. Switch to the `root` user
sudo su

# 2.1. Set a password for the root user
passwd root

okineadev

sudo wget -qO- https://get.docker.com/ | sh

# Add the current user to the Docker group (allows running Docker without sudo)
sudo usermod -aG docker $USER

okineadev

subfinder -d myfritz.net -silent | while read sub; do
  if curl -Is --max-time 5 "http://$sub" > /dev/null; then
    echo "http://$sub:83/view/index.shtml"
  fi
done

okineadev

#!/usr/bin/env bash

curl -s https://github.com/OWNER/REPO | grep -oE 'https://camo[^"]+' | while read i; do curl -X PURGE "$i"; done

okineadev

CONFIG_USB_STORAGE=m
CONFIG_USB_STORAGE_DEBUG=y
CONFIG_USB_STORAGE_REALTEK=m
CONFIG_REALTEK_AUTOPM=y
CONFIG_USB_STORAGE_DATAFAB=m
CONFIG_USB_STORAGE_FREECOM=m
CONFIG_USB_STORAGE_ISD200=m
CONFIG_USB_STORAGE_USBAT=m
CONFIG_USB_STORAGE_SDDR09=m
CONFIG_USB_STORAGE_SDDR55=m

okineadev

{
	"name": "some-cool-package",
	"version": "0.8.2",
	"description": "🚀 A modern toolkit for building awesome things",
	"main": "src/index.ts",
	"type": "module",
	"private": false,
	"author": {
		"name": "Example Developer",
		"email": "[email protected]",

okineadev

                                    ..                 
                          ..=+=+*==.:=-=..             
                       .:%=-.*#*=*#++**@#...           
                     .-@.:-*..     ..-=*#:*.           
                     +-+=:.             ...:=.         
                    ==@%%:....              .#.        
                  ..#*+#=**##..              ::.       
                .:--@+*+*+***+. .-.....==-... .-.      
            ....:%+%+%*-%%+*%. .::+@%%#..::*+..*..     
         .-+.:...+%:***@+***:...#=...:-+@+#=#+#:#.     

okineadev

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."
  }
]