See how a minor change to your commit message style can make a difference. Examples
Have a look at CLI util git-conventional-commits to ensure this conventions and generate changelogs
See how a minor change to your commit message style can make a difference. Examples
Have a look at CLI util git-conventional-commits to ensure this conventions and generate changelogs
const http = require("http"); | |
const esbuild = require("esbuild"); | |
const serve = async (servedir, listen) => { | |
// Start esbuild's local web server. Random port will be chosen by esbuild. | |
const { host, port } = await esbuild.serve({ servedir }, {}); | |
// Create a second (proxy) server that will forward requests to esbuild. | |
const proxy = http.createServer((req, res) => { | |
// forwardRequest forwards an http request through to esbuid. |
This is a basic implementation of the game Tetris, but it's missing a few things intentionally and they're left as further exploration for the reader.
OS version is in system_profiler_SPSoftwareDataType.txt
;
Utilities in /bin
are listed in bin.txt
;
Utilities in /sbin
are listed in sbin.txt
;
Utilities in /usr/bin
are listed in usr_bin.txt
;
Utilities in /usr/sbin
are listed in usr_sbin.txt
;
Utilities in /usr/libexec
are listed in usr_libexec.txt
;
Default paths are
/usr/local/bin
brew install fish
curl -L https://get.oh-my.fish | fish
Sometimes you want to have a subdirectory on the master
branch be the root directory of a repository’s gh-pages
branch. This is useful for things like sites developed with Yeoman, or if you have a Jekyll site contained in the master
branch alongside the rest of your code.
For the sake of this example, let’s pretend the subfolder containing your site is named dist
.
Remove the dist
directory from the project’s .gitignore
file (it’s ignored by default by Yeoman).
name: Build and Deploy to Pages | |
on: | |
push: | |
branches: ['main'] | |
jobs: | |
build: | |
runs-on: ubuntu-latest |
There are certain files created by particular editors, IDEs, operating systems, etc., that do not belong in a repository. But adding system-specific files to the repo's .gitignore
is considered a poor practice. This file should only exclude files and directories that are a part of the package that should not be versioned (such as the node_modules
directory) as well as files that are generated (and regenerated) as artifacts of a build process.
All other files should be in your own global gitignore file:
.gitignore
in your home directory and add any filepath patterns you want to ignore.Note: The specific name and path you choose aren't important as long as you configure git to find it, as shown below. You could substitute
.config/git/ignore
for.gitignore
in your home directory, if you prefer.