Handling and migration of original project issues about jwt HOT 6 CLOSED

Note that is is important to keep notified the original reporter, either by reference via addendum on the migrated issue or by CCing then via a new comment in the thread

from jwt.

It should be noted that github at some point added the feature to transfer issues from one repo to another, although this should be done by @dgrijalva (and for each of the 90 issues, so I don't think it's a plausible effort for now):

from jwt.

I guess we can triage issues on the other repo, make a placeholder here with a linkback to the origonal repo and work from there to begin with?

from jwt.

@Waterdrips I agree on doing it manually. It'll be a chore but it'll be less prone to errors

I'm on a pretty tight schedule until this Q ends so I´ll see what I can do on these fronts

from jwt.

I've finished a check on the legacy repo issued and migrated those that still apply to this fork (and are not duplicates) with the label jwt-go: legacy

from jwt.

Also, people may overlook the README and description on the legacy repo so issues may still arise on there like this one dgrijalva/jwt-go#478. Authors shall be redirected here

from jwt.