Kim J. Nordmo AdmiringWorm

Update-AUPackages

UTC: 2026-03-08 02:20 AdmiringWorm/chocolatey-packages

This file is automatically generated by the update_all.ps1 script using the Chocolatey-AU module.

Ignored | History | Force Test | [Releases](https://github.com/AdmiringWor

Update-AUPackages

UTC: 2025-09-27 17:36 AdmiringWorm/chocolatey-packages

This file is automatically generated by the update_all.ps1 script using the Chocolatey-AU module.

Ignored | History | Force Test | [Releases](https://github.com/AdmiringWorm/

Keybase proof

I hereby claim:

I am admiringworm on github.
I am admiringworm (https://keybase.io/admiringworm) on keybase.
I have a public key ASAH0Z3vgl7IWAqRG-zmoqyRK7RXpg3T02jDwzEAHQnLEwo

To claim this, I am signing this object:

Environment variables set when powershell script is running through choco

NOTE: All of the following variables need to be prefixed with $env:

CHOCOLATEY_VERSION: 0.10.3.0
CHOCOLATEY_VERSION_PRODUCT: 0.10.3 (EXPERIMENTAL)
ChocolateyForce - $true if the user passed --force when installing, otherwise not set
ChocolateyInstall - Set to the path where choco is installed.
chocolateyInstallArguments - The extra arguments the user have passed to the installer (EXPERIMENTAL)
chocolateyInstallOverride - $true if the user passed --notsilent (EXPERIMENTAL)
ChocolateyPackageFolder - The path to where the package content is cached

List of aliases that are Read-Only in Powershell V2

PS C:\Users\Administrator> gal | ? { $_.options -match 'readonly' } | ft Name,Definition -a

Name    Definition
----    ----------
%       ForEach-Object
?       Where-Object
ac      Add-Content

What can you do as a maintainer?

The goal of this gist is to provide some details on what you can do and can't do on chocolatey.org when you are a maintainer.

You can not remove yourself as a maintainer for packages available on chocolatey.org. You will need to contact the site admins to be removed from a package. You will not be removed as a maintainer if you are the only maintainer listed.
When a new package have been pushed to chocolatey.org, a new version of the same package can not be pushed until the existing version is either approved or rejected. If the package is failing, the recommended solution is to update the existing version which fixes the failure reason. When this isn't possible, you can rejected a failing version yourself, or ask a Moderator to rejected it.

	#!/bin/sh

	if git rev-parse --verify HEAD >/dev/null 2>&1
	then
	against=HEAD
	else
	# Initial commit: diff against an empty tree object
	against=4b825dc642cb6eb9a060e54bf8d69288fbee4904
	fi

	Usage: dotnet add [arguments] [options] [command]

	Arguments:
	<PROJECT> The project file to operate on. If a file is not specified, the command will search the current directory for one.

	Options:
	-h\|--help Show help information

	Commands:
	package Command to add package reference

	#load "./modules.cake"

	#if !CUSTOM_CODECOV
	Setup<CodecovSettings>((context) => {
	var settings = new CodecovSettings {
	Required = true
	};

	if (BuildParameters.Version != null && !string.IsNullOrEmpty(BuildParameters.Version.FullSemVersion) && BuildParameters.IsRunningOnAppVeyor) {
	// Required to work correctly with appveyor because environment changes isn't detected until cake is done running.

	{
	"workbench.colorCustomizations": {
	"activityBar.background": "#aacdec",
	"activityBar.activeBorder": "#6F3215",
	"activityBar.foreground": "#242c5c",
	"activityBar.inactiveForeground": "#242c5c99",
	"activityBarBadge.background": "#6F3215",
	"activityBarBadge.foreground": "#e7e7e7",
	"titleBar.activeBackground": "#80b5e3",
	"titleBar.inactiveBackground": "#80b5e399",