Easily build, run tests and coverage, cross-compile, package and publish your .NET library or application to NuGet and GitHub.

Server Driven UI library for dotnet MAUI. New features to be deployed on all platforms simultaneously via a backend change, without releasing new versions of the native apps.

# Git Credential Manager [](https://github.com/GitCredentialManager/git-credential-manager/actions/workflows/continuous-integration.yml) --- [Git Credential Manager](https://github.com/GitCredentialManager/git-credential-manager) (GCM) is a secure Git credential helper built on [.NET](https://dotnet.microsoft.com) that runs on Windows, macOS, and Linux. Compared to Git's [built-in credential helpers]((https://git-scm.com/book/en/v2/Git-Tools-Credential-Storage)) (Windows: wincred, macOS: osxkeychain, Linux: gnome-keyring/libsecret) which provides single-factor authentication support working on any HTTP-enabled Git repository, GCM provides multi-factor authentication support for [Azure DevOps](https://dev.azure.com/), Azure DevOps Server (formerly Team Foundation Server), GitHub, Bitbucket, and GitLab. Git Credential Manager (GCM) replaces the .NET Framework-based [Git Credential Manager for Windows](https://github.com/microsoft/Git-Credential-Manager-for-Windows) (GCM), and the Java-based [Git Credential Manager for Mac and Linux](https://github.com/microsoft/Git-Credential-Manager-for-Mac-and-Linux) (Java GCM), providing a consistent authentication experience across all platforms. ## Current status Git Credential Manager is currently available for Windows, macOS, and Linux\*. GCM only works with HTTP(S) remotes; you can still use Git with SSH: - [Azure DevOps SSH](https://docs.microsoft.com/en-us/azure/devops/repos/git/use-ssh-keys-to-authenticate?view=azure-devops) - [GitHub SSH](https://help.github.com/en/articles/connecting-to-github-with-ssh) - [Bitbucket SSH](https://confluence.atlassian.com/bitbucket/ssh-keys-935365775.html) Feature|Windows|macOS|Linux -|:-:|:-:|:-: Installer/uninstaller|&#10003;|&#10003;|&#10003;\* Secure platform credential storage|&#10003; [(see more)](docs/credstores.md)|&#10003; [(see more)](docs/credstores.md)|&#10003; [(see more)](docs/credstores.md) Multi-factor authentication support for Azure DevOps|&#10003;|&#10003;|&#10003; Two-factor authentication support for GitHub|&#10003;|&#10003;|&#10003; Two-factor authentication support for Bitbucket|&#10003;|&#10003;|&#10003; Two-factor authentication support for GitLab|&#10003;|&#10003;|&#10003; Windows Integrated Authentication (NTLM/Kerberos) support|&#10003;|_N/A_|_N/A_ Basic HTTP authentication support|&#10003;|&#10003;|&#10003; Proxy support|&#10003;|&#10003;|&#10003; `amd64` support|&#10003;|&#10003;|&#10003; `x86` support|&#10003;|_N/A_|&#10007; `arm64` support|best effort|via Rosetta 2|best effort, no packages `armhf` support|_N/A_|_N/A_|best effort, no packages (\*) GCM guarantees support for the below Linux distributions. GCM maintainers also monitor and evaluate issues opened against other distributions to determine community interest/engagement and whether an emerging platform should become fully-supported. - Debian/Ubuntu/Linux Mint - Fedora/CentOS/RHEL - Alpine ## Download and Install ### macOS Homebrew The preferred installation mechanism is using Homebrew; we offer a Cask in our custom Tap. To install, run the following: ```shell brew tap microsoft/git brew install --cask git-credential-manager-core ``` After installing you can stay up-to-date with new releases by running: ```shell brew upgrade git-credential-manager-core ``` #### Git Credential Manager for Mac and Linux (Java-based GCM) If you have an existing installation of the 'Java GCM' on macOS and you have installed this using Homebrew, this installation will be unlinked (`brew unlink git-credential-manager`) when GCM is installed. #### Uninstall To uninstall, run the following: ```shell brew uninstall --cask git-credential-manager-core ``` --- ### macOS Package We also provide a [.pkg installer](https://github.com/GitCredentialManager/git-credential-manager/releases/latest) with each release. To install, double-click the installation package and follow the instructions presented. #### Uninstall To uninstall, run the following: ```shell sudo /usr/local/share/gcm-core/uninstall.sh ``` --- <!-- this explicit anchor should stay stable so that external docs can link here --> <!-- markdownlint-disable-next-line no-inline-html --> <a name="linux-install-instructions"></a> ### Linux #### Experimental: install from source helper script If you would like to help dogfood our new install from source helper script, run the following: 1. To ensure `curl` is installed: ```shell curl --version ``` If `curl` is not installed, please use your distribution's package manager to install it. 1. To download and run the script: ```shell curl -LO https://raw.githubusercontent.com/GitCredentialManager/git-credential-manager/main/src/linux/Packaging.Linux/install-from-source.sh && sh ./install-from-source.sh && git-credential-manager-core configure ``` **Note:** You will be prompted to enter your credentials so that the script can download GCM's dependencies using your distribution's package manager. #### Ubuntu/Debian distributions Download the latest [.deb package](https://github.com/GitCredentialManager/git-credential-manager/releases/latest), and run the following: ```shell sudo dpkg -i <path-to-package> git-credential-manager-core configure ``` **Note:** Although packages were previously offered on certain [Microsoft Ubuntu package feeds](https://packages.microsoft.com/repos/), GCM no longer publishes to these repositories. Please install the Debian package using the above instructions instead. To uninstall: ```shell git-credential-manager-core unconfigure sudo dpkg -r gcmcore ``` #### Other distributions Download the latest [tarball](https://github.com/GitCredentialManager/git-credential-manager/releases/latest), and run the following: ```shell tar -xvf <path-to-tarball> -C /usr/local/bin git-credential-manager-core configure ``` To uninstall: ```shell git-credential-manager-core unconfigure rm $(command -v git-credential-manager-core) ``` **Note:** all Linux distributions [require additional configuration](https://aka.ms/gcm/credstores) to use GCM. --- ### Windows GCM is included with [Git for Windows](https://gitforwindows.org/), and the latest version is included in each new Git for Windows release. This is the preferred way to install GCM on Windows. During installation you will be asked to select a credential helper, with GCM being set as the default.  #### Standalone installation You can also download the [latest installer](https://github.com/GitCredentialManager/git-credential-manager/releases/latest) for Windows to install GCM standalone. **:warning: Important :warning:** Installing GCM as a standalone package on Windows will forcibly override the version of GCM that is bundled with Git for Windows, **even if the version bundled with Git for Windows is a later version**. There are two flavors of standalone installation on Windows: - User (preferred) (`gcmcoreuser-win*`): Does not require administrator rights. Will install only for the current user and updates only the current user's Git configuration. - System (`gcmcore-win*`): Requires administrator rights. Will install for all users on the system and update the system-wide Git configuration. To install, double-click the desired installation package and follow the instructions presented. #### Uninstall (Windows 10) To uninstall, open the Settings app and navigate to the Apps section. Select "Git Credential Manager" and click "Uninstall". #### Uninstall (Windows 7-8.1) To uninstall, open Control Panel and navigate to the Programs and Features screen. Select "Git Credential Manager" and click "Remove". #### Windows Subsystem for Linux (WSL) Git Credential Manager can be used with the [Windows Subsystem for Linux (WSL)](https://aka.ms/wsl) to enable secure authentication of your remote Git repositories from inside of WSL. [Please see the GCM on WSL docs](docs/wsl.md) for more information. ## Supported Git versions Git Credential Manager tries to be compatible with the broadest set of Git versions (within reason). However there are some know problematic releases of Git that are not compatible. - Git 1.x The initial major version of Git is not supported or tested with GCM. - Git 2.26.2 This version of Git introduced a breaking change with parsing credential configuration that GCM relies on. This issue was fixed in commit [`12294990`](https://github.com/git/git/commit/12294990c90e043862be9eb7eb22c3784b526340) of the Git project, and released in Git 2.27.0. ## How to use Once it's installed and configured, Git Credential Manager is called implicitly by Git. You don't have to do anything special, and GCM isn't intended to be called directly by the user. For example, when pushing (`git push`) to [Azure DevOps](https://dev.azure.com), [Bitbucket](https://bitbucket.org), or [GitHub](https://github.com), a window will automatically open and walk you through the sign-in process. (This process will look slightly different for each Git host, and even in some cases, whether you've connected to an on-premises or cloud-hosted Git host.) Later Git commands in the same repository will re-use existing credentials or tokens that GCM has stored for as long as they're valid. Read full command line usage [here](docs/usage.md). ### Configuring a proxy See detailed information [here](https://aka.ms/gcm/httpproxy). ## Additional Resources - [Frequently asked questions](docs/faq.md) - [Development and debugging](docs/development.md) - [Command-line usage](docs/usage.md) - [Configuration options](docs/configuration.md) - [Environment variables](docs/environment.md) - [Enterprise configuration](docs/enterprise-config.md) - [Network and HTTP configuration](docs/netconfig.md) - [Credential stores](docs/credstores.md) - [Architectural overview](docs/architecture.md) - [Host provider specification](docs/hostprovider.md) - [Azure Repos OAuth tokens](docs/azrepos-users-and-tokens.md) - [GitLab support](docs/gitlab.md) ## Experimental Features - [Windows broker (experimental)](docs/windows-broker.md) ## Contributing This project welcomes contributions and suggestions. See the [contributing guide](CONTRIBUTING.md) to get started. This project follows [GitHub's Open Source Code of Conduct](CODE_OF_CONDUCT.md). ## License We're [MIT](LICENSE) licensed. When using GitHub logos, please be sure to follow the [GitHub logo guidelines](https://github.com/logos).

Bot Auto Checkout Flashsale Shopee Promo versi 2. Feature : Auto Login. Auto Checkout. Bahan untuk di Pc : Net framework 4.8 : https://dotnet.microsoft.com/download/dotnet-framework/net48 Install python versi 3.7, versi terbaru lebih baik : https://www.python.org/downloads Install semua pip yang ada di readme.md Tambahan : pip install pynput dan pyautogui. Google Chrome versi terbaru 2020 (86.0.4240.198) karena web driver chrome saya versi terbaru : https://www.google.com/chrome/?brand=YTUH&gclid=Cj0KCQiAnb79BRDgARIsAOVbhRp0LvXN5YffCPcNTtcorz6j-5Y-z-Kfh7Yx1knyGgl_mgG-sVPSKtoaAs81EALw_wcB&gclsrc=aw.ds. Cara pakai : Extract file BotacsPro2.rar di Localdisk C. Setting waktu di script BotacsPro.py : menit= detik=5 > ubah waktu sesuai countdown shopee, kalau perlu kurang 1 - 3 detik lebih cepat. Setting akun shopee, tidak boleh ada verifikasi sms, supaya bot eksekusi langsung masuk dan tinggal bayar saja. Setting akun di akun.txt Cek script autorun.bat untuk setting lokasi dan cek lokasi apakah sudah benar. Jika, sudah benar semua, buka folder BotacsPro2 di Localdisk C > Release > AutoRunCMD.exe Klik 2x AutoRunCMD.exe Selesai, selamat kalian sudah menggunakan bot ini. Selamat menikmati ^-^. Untuk di handphone : Download BotacsPro2 dan extract ke SD card atau ke internal memori. Install Python versi 3.7 di termux. Download termux di Google Playstore. Buka aplikasi termux. Install semua pip yang ada di readme.md Tambahan : pip install pynput dan pyautogui. Setting akun di akun.txt Update Google Chrome ke versi 86.0.4240.198. ubah script .bat untuk mengganti lokasi script. Exsekusi script bat : bat autorun.bat , untuk info selengkapnya bisa google saja. Selesai.

Sample to version and release dotnet application using conventional commits.

Publish your dotnet app (WinUI 3, WPF, Console) as a zip file with auto changelog in Github Release with Github Action.

An easier way to add nvidia control panel in DCH drivers. The file is in .net 7 but using AOT so you don't need to install the net api. To use run nvidiapanel.exe if you want to do your own build use the command "dotnet publish -r win-x64 -c Release" in terminal and after exit the final file will be "net7.0\win-x64-native".

dotnet core console app that generates release notes from pull requests for the UWP Community Toolkit

# # This is free software, lisence use MIT. # # Copyright (C) 2019 P3TERX <https://p3terx.com> # Copyright (C) 2019 KFERMercer <KFER.Mercer@gmail.com> # # <https://github.com/KFERMercer/OpenWrt-CI> # name: OpenWrt-CI on: push: branches: - master # schedule: # - cron: 0 20 * * * # release: # types: [published] jobs: build: runs-on: ubuntu-latest steps: - name: Checkout uses: actions/checkout@master with: ref: master - name: Initialization environment env: DEBIAN_FRONTEND: noninteractive run: | docker rmi `docker images -q` echo "Deleting files, please wait ..." sudo rm -rf \ /usr/share/dotnet \ /etc/mysql \ /etc/php sudo -E apt-get -y purge \ azure-cli \ ghc* \ zulu* \ hhvm \ llvm* \ firefox \ google* \ dotnet* \ powershell \ openjdk* \ mysql* \ php* sudo -E apt-get update sudo -E apt-get -y install build-essential asciidoc binutils bzip2 gawk gettext git libncurses5-dev libz-dev patch unzip zlib1g-dev lib32gcc1 libc6-dev-i386 subversion flex uglifyjs git-core gcc-multilib p7zip p7zip-full msmtp libssl-dev texinfo libglib2.0-dev xmlto qemu-utils upx libelf-dev autoconf automake libtool autopoint device-tree-compiler sudo -E apt-get -y autoremove --purge sudo -E apt-get clean - name: Update feeds run: | ./scripts/feeds update -a ./scripts/feeds install -a - name: Costom configure file run: | rm -f ./.config* touch ./.config # # ========================固件定制部分======================== # # # 如果不对本区块做出任何编辑, 则生成默认配置固件. # # 以下为定制化固件选项和说明: # # # 有些插件/选项是默认开启的, 如果想要关闭, 请参照以下示例进行编写: # # ========================================= # | # 取消编译VMware镜像: | # | cat >> .config <<EOF | # | # CONFIG_VMDK_IMAGES is not set | # | EOF | # ========================================= # # # 以下是一些提前准备好的一些插件选项. # 直接取消注释相应代码块即可应用. 不要取消注释代码块上的汉字说明. # 如果不需要代码块里的某一项配置, 只需要删除相应行. # # 如果需要其他插件, 请按照示例自行添加. # 注意, 只需添加依赖链顶端的包. 如果你需要插件 A, 同时 A 依赖 B, 即只需要添加 A. # # 无论你想要对固件进行怎样的定制, 都需要且只需要修改 EOF 回环内的内容. # # 编译x64固件: # cat >> .config <<EOF # CONFIG_TARGET_x86=y # CONFIG_TARGET_x86_64=y # CONFIG_TARGET_x86_64_Generic=y # EOF # 固件压缩: # cat >> .config <<EOF # CONFIG_TARGET_IMAGES_GZIP=y # EOF # 编译UEFI固件: # cat >> .config <<EOF # CONFIG_EFI_IMAGES=y # EOF # IPv6支持: # cat >> .config <<EOF # CONFIG_PACKAGE_dnsmasq_full_dhcpv6=y # CONFIG_PACKAGE_ipv6helper=y # EOF # 多文件系统支持: # cat >> .config <<EOF # CONFIG_PACKAGE_kmod-fs-nfs=y # CONFIG_PACKAGE_kmod-fs-nfs-common=y # CONFIG_PACKAGE_kmod-fs-nfs-v3=y # CONFIG_PACKAGE_kmod-fs-nfs-v4=y # CONFIG_PACKAGE_kmod-fs-ntfs=y # CONFIG_PACKAGE_kmod-fs-squashfs=y # EOF # USB3.0支持: # cat >> .config <<EOF # CONFIG_PACKAGE_kmod-usb-ohci=y # CONFIG_PACKAGE_kmod-usb-ohci-pci=y # CONFIG_PACKAGE_kmod-usb2=y # CONFIG_PACKAGE_kmod-usb2-pci=y # CONFIG_PACKAGE_kmod-usb3=y # EOF # 常用LuCI插件选择: # cat >> .config <<EOF # CONFIG_PACKAGE_luci-app-adbyby-plus=y # CONFIG_PACKAGE_luci-app-aria2=y # CONFIG_PACKAGE_luci-app-baidupcs-web=y # CONFIG_PACKAGE_luci-app-docker=y # CONFIG_PACKAGE_luci-app-frpc=y # CONFIG_PACKAGE_luci-app-hd-idle=y # CONFIG_PACKAGE_luci-app-kodexplorer=y # CONFIG_PACKAGE_luci-app-minidlna=y # CONFIG_PACKAGE_luci-app-openvpn=y # CONFIG_PACKAGE_luci-app-openvpn-server=y # CONFIG_PACKAGE_luci-app-qbittorrent=y # CONFIG_PACKAGE_luci-app-ssr-plus_INCLUDE_Kcptun=y # CONFIG_PACKAGE_luci-app-ssr-plus_INCLUDE_Shadowsocks=y # CONFIG_PACKAGE_luci-app-ssr-plus_INCLUDE_ShadowsocksR_Server=y # CONFIG_PACKAGE_luci-app-ssr-plus_INCLUDE_ShadowsocksR_Socks=y # CONFIG_PACKAGE_luci-app-ssr-plus_INCLUDE_V2ray=y # CONFIG_PACKAGE_luci-app-ttyd=y # CONFIG_PACKAGE_luci-app-v2ray-server=y # CONFIG_PACKAGE_luci-app-verysync=y # CONFIG_PACKAGE_luci-app-webadmin=y # CONFIG_PACKAGE_luci-app-wireguard=y # CONFIG_PACKAGE_luci-app-wrtbwmon=y # EOF # LuCI主题: # cat >> .config <<EOF # CONFIG_PACKAGE_luci-theme-argon=y # CONFIG_PACKAGE_luci-theme-netgear=y # EOF # 常用软件包: # cat >> .config <<EOF # CONFIG_PACKAGE_curl=y # CONFIG_PACKAGE_htop=y # CONFIG_PACKAGE_nano=y # CONFIG_PACKAGE_screen=y # CONFIG_PACKAGE_tree=y # CONFIG_PACKAGE_vim-fuller=y # CONFIG_PACKAGE_wget=y # EOF # 取消编译VMware镜像以及镜像填充 (不要删除被缩进的注释符号): # cat >> .config <<EOF # # CONFIG_TARGET_IMAGES_PAD is not set # # CONFIG_VMDK_IMAGES is not set # EOF # # ========================固件定制部分结束======================== # sed -i 's/^[ \t]*//g' ./.config make defconfig - name: Make download run: | make download -j8 find dl -size -1024c -exec ls -l {} \; find dl -size -1024c -exec rm -f {} \; - name: Compile firmware run: | echo -e "$(nproc) thread build." make -j$(nproc) V=s - name: Assemble artifact run: | rm -rf ./artifact/ mkdir -p ./artifact/ find ./bin/targets/ -name "*combined*img*" | xargs -i mv -f {} ./artifact/ find ./bin/targets/ -name "*sysupgrade*bin*" | xargs -i mv -f {} ./artifact/ - name: Upload artifact uses: actions/upload-artifact@master with: name: OpenWrt firmware path: ./artifact/

A dotnet tool for repackaging pre-release NuGet packages. This tool also provides options for updating associated files.

SmartHireOps is a Microsoft Azure cloud hosted AI-driven HR recruitment platform integrating DevOps practices. With AI powered profile verification, Kubernetes orchestration, and a Dotnet/React stack, it streamlines the hiring process. Stay tuned for new releases, and though contributions aren't open yet, feedback is welcome.

An easier way to use the debloat proposed by amitxv instead of having to use linux. The file is in .net 7 but using AOT so you don't need to install the net api. To use run start.bat. if you want to do your own build use the command "dotnet publish -r win-x64 -c Release" in terminal and after exit the final file will be "net7.0\win-x64-native".

Semantic release plugin for dotnet (nuget) projects

🚀 Add DotNet versioning and NuGet publishing to Release It

A simple dotnet global tool to tag releases in semver

Use github releases to publish and deploy serverless framework dotnet projects

Reusable sources for build, test, release automation of PowerShell modules, written in DotNet/C# or PowerShell.

A simple QRCode Encoder in .NET using ZXing and published as an Azure API App. (prior dotnet versions available for download in prior releases)

RU: Релизная версия "SnakeGame" Системные требования: Windows 10, .NET Core 3.1(https://dotnet.microsoft.com/en-us/download/dotnet/3.1/runtime?cid=getdotnetcore). Чтобы скачать нажмите на "Code" и в выпадающем меню нажать "Download ZIP". EN: Release version of "SnakeGame". System requirements: Windows 10, .NET Core 3.1(https://dotnet.microsoft.com/en-us/download/dotnet/3.1/runtime?cid=getdotnetcore). To download click on "Code" and in the drop-down menu click on "Download ZIP".

This is a modification of the new ValueTuple released with C# 7, adapted to work in .NET 3.5 or greater (and therefore usable in Unity). Original: https://github.com/dotnet/corefx/blob/master/src/System.ValueTuple/src/System/ValueTuple/ValueTuple.cs

A very simple, easily auditable XOR calculator in .NET Core 3.0. Intended for anyone interested in generating wallets in a bit more secure fashion. Also I'd be curious to know why nobody seems to have thought of combining entropies like this before me. Does everyone really trust black-boxes? Build using .NET Core 3: dotnet build -c Release

Demo of use https://github.com/xoofx/dotnet-releaser

No description available

test-dotnet-release

Testing dotnet release process

Dotnet maui release test

dotnet pack --configuration Release

Check new releases of dotnet

Microsoft DotNet Mass Release Installer

Pre-release for prek dotnet support