FAQ about 502 error links to wrong issues #428
Comments
c3d
added a commit
to c3d/forge
that referenced
this issue
Oct 20, 2021
This fixes the link to issue magit#20 in `magit/forge` (and not `magit/ghub). Fixs: magit#428 Signed-off-by: Christophe de Dinechin <[email protected]>
c3d
added a commit
to c3d/forge
that referenced
this issue
Oct 20, 2021
This fixes the link to issue magit#20 in `magit/forge` (and not `magit/ghub`). Fixs: magit#428 Signed-off-by: Christophe de Dinechin <[email protected]>
tarsius
pushed a commit
to c3d/forge
that referenced
this issue
Oct 20, 2021
This fixes the link to issue magit#20 in `magit/forge` (and not `magit/ghub`). Fixs: magit#428 Signed-off-by: Christophe de Dinechin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
(Edited because
magit/forgeseems to have "eaten" the description I had typed)The FAQ about 502 errors points to issue #20 in
magit/ghubinstead ofmagit/forge. Issue magit/ghub#83 is in the right spot.The text was updated successfully, but these errors were encountered: