Ricardo Abreu ricab

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

Using `<details>` in GitHub

Suppose you're opening an issue and there's a lot noisey logs that may be useful.

Rather than wrecking readability, wrap it in a <details> tag!

<details>
 Summary Goes Here

IRC Reference

by xero updated 10.29.24

Whether you're trying to give back to the open source community or collaborating on your own projects, knowing how to properly fork and generate pull requests is essential. Unfortunately, it's quite easy to make mistakes or not know what you should do when you're initially learning the process. I know that I certainly had considerable initial trouble with it, and I found a lot of the information on GitHub and around the internet to be rather piecemeal and incomplete - part of the process described here, another there, common hangups in a different place, and so on.

In an attempt to coallate this information for myself and others, this short tutorial is what I've found to be fairly standard procedure for creating a fork, doing your work, issuing a pull request, and merging that pull request back into the original project.

Creating a Fork

Just head over to the GitHub page and click the "Fork" button. It's just that simple. Once you've done that, you can use your favorite git client to clone your repo or j

All github Emoji (Smiles)

ali.md/emoji

| 😄 | 😆 | 😊 | 😃 | ☺️ | 😏 | 😍 | 😘 | :kissing_face: | 😳 | 😌 | 😆 | 😁 | 😉 | :wink2: | 👅 | 😒 | 😅 | 😓

😩 | 😔 | 😞 | 😖 | 😨 | 😰 | 😣 | 😢 | 😭 | 😂 | 😲 | 😱 | | 😫 | 😠 | 😡 | 😤 | 😪 | 😋 | 😷

😎 | 😵 | 👿 | 😈 | 😐 | 😶 | 😇 | 👽 | 💛 | 💙 | 💜 | ❤️ | 💚 | 💔 | 💓 | 💗 | 💕 | 💞 | 💘 | ✨

	#!/usr/bin/env bash

	# --slave /usr/bin/$1 $1 /usr/bin/$1-\${version} \\

	function register_clang_version {
	local version=$1
	local priority=$2

	update-alternatives \
	--install /usr/bin/llvm-config llvm-config /usr/bin/llvm-config-${version} ${priority} \

	#!/usr/bin/env python3
	# -- coding: utf-8 --
	# Copyright (C) 2015-2017 Carlos Jenkins <[email protected]>
	#
	# Licensed under the Apache License, Version 2.0 (the "License");
	# you may not use this file except in compliance with the License.
	# You may obtain a copy of the License at
	#
	# http://www.apache.org/licenses/LICENSE-2.0
	#

	#!/bin/sh
	#
	# An example hook script to verify what is about to be committed.
	# Called by "git commit" with no arguments. The hook should
	# exit with non-zero status after issuing an appropriate message if
	# it wants to stop the commit.
	#
	# Usage:
	# Remove the .sh file extension when you put the script in your hooks folder!
	#

	List just aliases
	$ git config --get-regexp alias

	List all config parameters
	$ git config --list

	git reflog show master
	git reset --keep master@{1}