Location - The location of the application. Usually just a URL, but the location can contain multiple pieces of information that can be used by an app
pathname - The "file/directory" portion of the URL, like invoices/123
search - The stuff after ? in a URL like /assignments?showGrades=1.
query - A parsed version of search, usually an object but not a standard browser feature.
hash - The # portion of the URL. This is not available to servers in request.url so its client only. By default it means which part of the page the user should be scrolled to, but developers use it for various things.
state - Object associated with a location. Think of it like a hidden URL query. It's state you want to keep with a specific location, but you don't want it to be visible in the URL.
Implementation notes on react's scheduling model as of (shortly before) 16.8.0
While the public API intended for users to use is the scheduler package, the
reconciler currently does not use scheduler's priority classes internally.
ReactFiberScheduler has its own internal "mini-scheduler" that uses the
scheduler package indirectly for its deadline-capable scheduleCallback.
This is kind of a documentation of implementation details that I suppose will be
gone by the end of the year, but what can you do.
Now add the line fetch = +refs/pull/*/head:refs/remotes/origin/pr/* to this section. Obviously, change the github url to match your project's URL. It ends up looking like this: