IntuneGet Logo
IntuneGet
Documentation

GitHub Setup

Optional GitHub Actions pipeline for cloud-based packaging. The local packager is now the recommended approach for most deployments.

Local Packager Recommended

Starting with v0.5, IntuneGet includes a local packager service that runs on a Windows machine and handles all app packaging locally. This eliminates the need for GitHub Actions and provides faster packaging with no usage limits. See the Getting Started guide for local packager setup.

Local Packager

  • No usage limits or costs
  • Faster packaging (no cloud roundtrip)
  • Simple API key authentication
  • Works entirely on your infrastructure

GitHub Actions

  • 2,000 free minutes/month (private repos)
  • No local Windows machine required
  • Good for testing or low-volume use
  • Requires PAT and repository setup

GitHub Actions Setup (Optional)

If you prefer GitHub Actions for packaging, or want it as a fallback, follow these steps:

1

Fork the Repository

  1. Go to github.com/ugurkocde/IntuneGet
  2. Click Fork in the top right
  3. Select your account/organization
2

Configure Repository Secrets

Navigate to your fork: Settings > Secrets and variables > Actions

Secret NameDescription
AZURE_CLIENT_IDEntra ID Application ID
AZURE_CLIENT_SECRETEntra ID Client Secret
CALLBACK_SECRETWebhook verification (must match your .env)
3

Enable Actions & Create PAT

  1. Go to the Actions tab and enable workflows
  2. Create a PAT at github.com/settings/tokens
  3. Required scopes: repo + workflow
4

Update Environment

bash|.env.local
GITHUB_OWNER=your-github-username
GITHUB_REPO=IntuneGet
GITHUB_PAT=ghp_your-personal-access-token
CALLBACK_SECRET=same-secret-as-in-github

Cost Considerations

GitHub Actions Usage

  • Public repos: Free
  • Private repos: 2,000 minutes/month free, then $0.008/minute for Windows runners

Each packaging job typically takes 2-5 minutes. The local packager has no such limits.

Common Issues

Workflow not triggering

  • Verify PAT has correct scopes (repo + workflow)
  • Check workflow is enabled in the Actions tab
  • Verify GITHUB_OWNER and GITHUB_REPO are correct

Callback fails

  • Verify CALLBACK_SECRET matches in both places
  • Check NEXT_PUBLIC_URL is accessible from GitHub
  • Review callback endpoint logs

Next Steps

Continue with Docker deployment to get your instance running.

Deploy with DockerGetting Started (Local Packager)