Pckgr
  • About Pckgr
    • Intro: What is Pckgr?
      • How Package Updates Work
      • PckgrBot
      • Homage to Winget
    • Applications Available
      • Request Application
    • Security of Pckgr
      • Microsoft Single Sign On
    • Pckgr Pricing Model
    • Feature Releases and Roadmap
      • Q1 2025 New Features Newsletter
  • Getting Started
    • Setting up your Dashboard
      • Signing Up
      • Managing Companies
      • Connecting Tenants
      • Adding Team Members
    • Creating Deployments
      • Application Library
        • Detect Applications from Intune with Pckgr
        • Application Status Tag
      • Repositories
        • Winget
        • Private Repository
          • Upgrading an Application to the Private Repository
        • MacOS
      • Deployment Settings
      • Application Management
  • Extra Features
    • Custom Applications
    • Cloning Intune Policies
  • INTEGRATIONS
    • Company Portal
    • Autopilot
    • Microsoft 365
  • Troubleshooting
    • Install Logs
    • Error Codes
    • Winget Issues
      • Winget Pre-Install
      • Winget CDN Issue
      • Repair Winget with PowerShell
    • Applications that Require to be Closed Before Updating
    • Frequently Asked Questions
  • SUPPORT
    • Pckgr ChatBot
    • Support Email
    • Delete your account
  • Policies
    • Privacy Policy
    • Terms of Service
Powered by GitBook
On this page
  1. About Pckgr
  2. Intro: What is Pckgr?

PckgrBot

Contributing to the Winget Repo

PreviousHow Package Updates WorkNextHomage to Winget

Last updated 2 months ago

At Pckgr, we always strive for efficiency, accuracy, and up-to-date content. PckgrBot, our internal automation tool, ensures that packages in the Winget GitHub repository are always current by scanning vendors for application updates.

Overview

PckgrBot is an in-house automation solution exclusively developed for the Pckgr team. Its primary role is to streamline the process of updating Winget packages by autonomously monitoring vendor application releases. It's currently in development and we are continually adding packages to the automation.

Key Features

  1. Vendor Scanning: Proactively detects any updates or changes to applications by frequently scanning vendors.

  2. Pull Request Automation: PckgrBot interfaces directly with the Winget GitHub repo to create pull requests with updated package manifests.

  3. Reduced Manual Intervention: Minimizes the manual work required by our team, ensuring that Winget packages remain up-to-date with minimal oversight.

How PckgrBot Operates

  1. Vendor Monitoring: PckgrBot starts its operation cycle by diligently scanning predefined vendor sites or platforms for any application updates.

  2. Update Identification: Upon detecting an update, the bot compiles necessary details readying it for the Winget repository.

  3. Winget Integration: Seamlessly creates a pull request in the Winget GitHub repository, proposing the package manifest update.

  4. Internal Notification: Once a pull request is initiated, the relevant internal team is notified to review, ensuring our high standards of quality and accuracy.

The Value of PckgrBot

  • Consistency: Guarantees that the packages we oversee in the Winget repo are regularly updated, maintaining a consistent and accurate package list.

  • Quality Assurance: The ability to take resolutions into our own hands if there are any issues with the Winget Repo.