Add repository content management functions #60

Activity

1. Marius Storhaug (MariusStorhaug)

   added this to GitHub PowerShell Moduleon Oct 7, 2023
2. Marius Storhaug (MariusStorhaug)

   converted this from a draft issue on Oct 7, 2023
3. Marius Storhaug (MariusStorhaug)

   added this to the 0.4 milestone on Oct 7, 2023
4. Marius Storhaug (MariusStorhaug)

   changed the title [-][Feature] Repositories - Repository contents - Manage Base64 encoded content in a repository[/-] [+][Feature] Repositories - Contents - Manage Base64 encoded content in a repository[/+] on Oct 7, 2023
5. Marius Storhaug (MariusStorhaug)

   removed this from the 0.4 milestone on Jan 26, 2025
6. Marius Storhaug (MariusStorhaug)

   self-assigned this

   on Apr 16, 2025
7. Marius Storhaug (MariusStorhaug)

   removed their assignment

   on Jun 19, 2025
8. Marius Storhaug (MariusStorhaug)

   changed the title [-][Feature] Repositories - Contents - Manage Base64 encoded content in a repository[/-] [+]Add repository content management functions[/+] on Apr 4, 2026
9. Marius Storhaug (MariusStorhaug)

   added

   featureNew featureNew feature

   minor

   on Apr 4, 2026
10. Marius Storhaug (MariusStorhaug)

    added the

    PBI

    issue type on Apr 4, 2026
11. MariusStorhaug commented on Jul 25, 2026

    

    Marius Storhaug (MariusStorhaug)

    on Jul 25, 2026

    MemberAuthor

    More actions

    Concrete consumer for this: MSXOrg/Custo (PR #1) currently distributes managed files by cloning every target repo on each run, which does not scale across a fleet. Content-management cmdlets would let it sync a single file via the API instead.

    Specific needs for that use case:

    • Get-GitHubRepositoryContent — GET /repos/{owner}/{repo}/contents/{path} (return content + sha).
    • Set-GitHubRepositoryContent — PUT /repos/{owner}/{repo}/contents/{path} (create/update; requires the existing blob sha on update, and supports a target branch).
    • Remove-GitHubRepositoryContent — DELETE /repos/{owner}/{repo}/contents/{path} (needed for convergence when a file is unsubscribed/removed).

    Idempotency matters: callers want to compare the desired bytes against the current blob and skip the write when unchanged, so returning the current sha/content from Get is important.