Mosh Feu moshfeu

## conventional-commits-cheatsheet.md

      
              1 file
            
          
              505 forks
            
          
                225 comments
              
            
              3115 stars
            
          
                qoomon
                / conventional-commits-cheatsheet.md
            
            
              Last active
              May 12, 2025 16:39
            
              
                Conventional Commits Cheatsheet
              
          
    Conventional Commit Messages 

See how a minor change to your commit message style can make a difference.
Tip
Take a look at git-conventional-commits , a CLI util to ensure these conventions, determine version and generate changelogs

Commit Message Formats

Default


## semantic-commit-messages.md

      
              1 file
            
          
              1188 forks
            
          
                372 comments
              
            
              7621 stars
            
          
                joshbuchea
                / semantic-commit-messages.md
            
            
              Last active
              May 12, 2025 13:04
            
              
                Semantic Commit Messages
              
          
    Semantic Commit Messages

See how a minor change to your commit message style can make you a better programmer.
Format: <type>(<scope>): <subject>
<scope> is optional
Example


## gist:1885435

      
              1 file
            
          
              867 forks
            
          
                188 comments
              
            
              2988 stars
            
          
                CristinaSolana
                / gist:1885435
            
            
              Created
              February 22, 2012 14:56
            
              
                Keeping a fork up to date
              
          
    1. Clone your fork:

git clone git@github.com:YOUR-USERNAME/YOUR-FORKED-REPO.git

2. Add remote from original repository in your forked repository:

cd into/cloned/fork-repo
git remote add upstream git://github.com/ORIGINAL-DEV-USERNAME/REPO-YOU-FORKED-FROM.git
git fetch upstream


## get-npm-package-version
# Version key/value should be on his own line
PACKAGE_VERSION=$(cat package.json \
  | grep version \
  | head -1 \
  | awk -F: '{ print $2 }' \
  | sed 's/[",]//g')

echo $PACKAGE_VERSION

## ffmpeg.md

      
              1 file
            
          
              298 forks
            
          
                45 comments
              
            
              1238 stars
            
          
                protrolium
                / ffmpeg.md
            
            
              Last active
              April 27, 2025 21:52
            
              
                ffmpeg guide
              
          
    ffmpeg

Converting Audio into Different Formats / Sample Rates

Minimal example: transcode from MP3 to WMA:

ffmpeg -i input.mp3 output.wma
You can get the list of supported formats with:

ffmpeg -formats
You can get the list of installed codecs with:


## Update remote repo
// Reference: http://www.blackdogfoundry.com/blog/moving-repository-from-bitbucket-to-github/
// See also: http://www.paulund.co.uk/change-url-of-git-repository

$ cd $HOME/Code/repo-directory
$ git remote rename origin bitbucket
$ git remote add origin https://github.com/mandiwise/awesome-new-repo.git
$ git push origin master

$ git remote rm bitbucket

## using-details-summary-github.md

      
              1 file
            
          
              9 forks
            
          
                54 comments
              
            
              81 stars
            
          
                scmx
                / using-details-summary-github.md
            
            
              Last active
              April 27, 2025 10:10
            
              
                Using <details> <summary> expandable content on GitHub with Markdown #details #summary #markdown #gfm #html
              
          
    How to use <details> <summary> expandable content on GitHub with Markdown

Firstly, what is <details> <summary>?

The HTML Details Element (<details>) creates a disclosure widget in which
information is visible only when the widget is toggled into an "open" state.
A summary or label can be provided using the <summary> element.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details.

Example


## repo-reset.md

      
              1 file
            
          
              214 forks
            
          
                121 comments
              
            
              762 stars
            
          
                heiswayi
                / repo-reset.md
            
            
              Created
              February 5, 2017 01:32
            
              
                GitHub - Delete commits history with git commands
              
          
    First Method

Deleting the .git folder may cause problems in our git repository. If we want to delete all of our commits history, but keep the code in its current state, try this:
# Check out to a temporary branch:
git checkout --orphan TEMP_BRANCH

# Add all the files:
git add -A


## load_dotenv.sh
# The initial version
if [ ! -f .env ]
then
  export $(cat .env | xargs)
fi

# My favorite from the comments. Thanks @richarddewit & others!
set -a && source .env && set +a

## Android Privacy Policy Template
<html>
<body>
<h2>Privacy Policy</h2>
<p>[Individual or Company Name] built the [App Name] app as a [open source | free | freemium | ad-supported | commercial] app. This SERVICE is provided by [Individual or company name] [at no cost] and is intended
    for use as is.</p>
<p>This page is used to inform website visitors regarding [my|our] policies with the collection, use, and
    disclosure of Personal Information if anyone decided to use [my|our] Service.</p>
<p>If you choose to use [my|our] Service, then you agree to the collection and use of information in
    relation with this policy. The Personal Information that [I|we] collect are used for providing and
    improving the Service. [I|We] will not use or share your information with anyone except as described
	# Version key/value should be on his own line
	PACKAGE_VERSION=$(cat package.json \
	\| grep version \
	\| head -1 \
	\| awk -F: '{ print $2 }' \
	\| sed 's/[",]//g')

	echo $PACKAGE_VERSION
	// Reference: http://www.blackdogfoundry.com/blog/moving-repository-from-bitbucket-to-github/
	// See also: http://www.paulund.co.uk/change-url-of-git-repository

	$ cd $HOME/Code/repo-directory
	$ git remote rename origin bitbucket
	$ git remote add origin https://github.com/mandiwise/awesome-new-repo.git
	$ git push origin master

	$ git remote rm bitbucket
	# The initial version
	if [ ! -f .env ]
	then
	export $(cat .env \| xargs)
	fi

	# My favorite from the comments. Thanks @richarddewit & others!
	set -a && source .env && set +a
	<html>
	<body>
	<h2>Privacy Policy</h2>
	<p>[Individual or Company Name] built the [App Name] app as a [open source \| free \| freemium \| ad-supported \| commercial] app. This SERVICE is provided by [Individual or company name] [at no cost] and is intended
	for use as is.</p>
	<p>This page is used to inform website visitors regarding [my\|our] policies with the collection, use, and
	disclosure of Personal Information if anyone decided to use [my\|our] Service.</p>
	<p>If you choose to use [my\|our] Service, then you agree to the collection and use of information in
	relation with this policy. The Personal Information that [I\|we] collect are used for providing and
	improving the Service. [I\|We] will not use or share your information with anyone except as described