Since a lot of the categories have many libraries listed, it would be helpful to highlight the top 2-4 "must use" libraries in each category, if appropriate.

I should figure out how to format this, and which ones I want to highlight.

Exposing category name as a "Change Template" variable would be useful for generating change logs in this format:

- ADDED: X (#100)
- ADDED: Y (#101)
- FIXED: Z (#99)

Relevant documentation:

Variable	Description
$CATEGORY	The category title of the pull request, e.g. Features.

As far as I know you can't do that with Replacers, as you only have one cat

Should these just be the same (ideally with the same code)? They are fairly similar, but with some difference, most notably the green/red in the equipper, and the list of stats in the info screen (which includes things like Cloaking and Nebula Resistance that are not visible on the equipping screen).

Currently certain PR's coming from forks result in the action running in the context of the fork, which means it can't post a comment or a PR review to the PR/issue.

Possible workarounds:

1. Report the size table back using a Status Check
   • Not sure if GitHub's UI will handle

This should fail because otherNum is not part of the State interface:

interface State {
  num: number
}

export const initialState: State = {
  num: 0
};

export const appsReducer = createReducer(initialState, handleAction => [
  handleAction(actions.getApps.success, () => ({
    num: 0,
    otherNum: 0 // adding this property should trigger a warning
  })),
]);