Skip to content

Unable to add app - because forking this repo does not seem to work #3675

Open

Description

@danieltrick

If I try to follow the instructions here, I run into the problem that the repo cannot be forked:

Image

This is not a temporary problem. Has been like that for several days 😟

Also, I am pretty usre that this is not a problem with my account, as I have forked various other repos without problem.

Regards.

Activity

  1. probonopd commented on Feb 10, 2026

    @probonopd
    Member

    Now that is an interesting one. Right now I am clueless about the cause.
    Thanks for reporting.

  2. zugaldia commented on Mar 22, 2026

    @zugaldia

    I just encountered the exact same problem.

  3. zugaldia commented on Mar 22, 2026

    @zugaldia

    I tried again to see if it was an intermittent issue, but I got the same error a few hours later. Looking at the Chrome Developer Console, these are the details I'm seeing:

    fetch-patch.ts:10 
     POST https://github.com/AppImage/appimage.github.io/new/master/data 422 (Unprocessable Content)
    o.cg.o.cg.fetch	@	fetch-patch.ts:10
    window.fetch	@	fetch-patch.ts:86
    s	@	verified-fetch.ts:30
    t	@	EditIssues.tsx:84
    s6	@	react-dom-client.production.js:12317
    (anonymous)	@	react-dom-client.production.js:12867
    tP	@	react-dom-client.production.js:1498
    un	@	react-dom-client.production.js:12455
    cd	@	react-dom-client.production.js:15306
    cc	@	react-dom-client.production.js:15274
    

    Opening the PR using the standard GitHub flow after manually forking does the trick.

  4. durandarthur commented on Nov 1, 2026

    @durandarthur

    Same issue on Firefox.

    Image

    I noted that there's no payload in the "Request" tab. No clue if that's normal.

  5. probonopd commented on Nov 2, 2026

    @probonopd
    Member

    All I can say is that we do get successful submissions, so some people seem to be able to fork this repository.

  6. durandarthur commented on Nov 2, 2026

    @durandarthur

    In the meantime, here's what I did with GitHub CLI:

    gh repo fork AppImage/appimage.github.io --clone=false
    
    base=$(gh api repos/[YOUR_GITHUB_USERNAME]/appimage.github.io/git/ref/heads/master --jq .object.sha)
    
    gh api -X POST repos/[YOUR_GITHUB_USERNAME]/appimage.github.io/git/refs -f ref=refs/heads/add-[YOUR_REPO_NAME] -f sha="$base"
    
    gh api -X PUT repos/[YOUR_GITHUB_USERNAME]/appimage.github.io/contents/data/[YOUR_REPO_NAME] \
        -f message="Add [YOUR_REPO_NAME]" -f branch=add-[YOUR_REPO_NAME] \
        -f content="$(echo 'https://github.com/[YOUR_GITHUB_USERNAME]/[YOUR_REPO_NAME]' | base64 -w0)"
    
    gh pr create --repo AppImage/appimage.github.io --base master --head [YOUR_GITHUB_USERNAME]:add-[YOUR_REPO_NAME] --title "Add [YOUR_REPO_NAME]"

    Note: Depending on your shell you might have some syntax errors with the base variable, just check the specifics for your shell

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions