Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add the github-linguist package #458

Merged
merged 2 commits into from
Apr 23, 2021
Merged

Conversation

aeisenberg
Copy link
Contributor

@aeisenberg aeisenberg commented Apr 22, 2021

This commit only adds a single package and all of its transitive
dependencies. The github-linguist package will be used for counting
lines of code as a baseline for databases we are analyzing.

The actual work to calculate the lines of code will come in a future PR.

This PR is surprisingly large and I'm not sure if that is a genuine
problem or not. The package-lock.json file has been upgraded from
v1 to v2 and this introduced some changes, but even when I tried to
install the package using and older version of npm, there were still
a large number of changes.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Confirm the readme has been updated if necessary.

@aeisenberg aeisenberg force-pushed the aeisenberg/add-github-linguist branch from c5d6cae to d2b4652 Compare April 22, 2021 22:54
@aeisenberg aeisenberg marked this pull request as draft April 22, 2021 22:54
This commit only adds a single package and all of its transitive
dependencies. The github-linguist package will be used for counting
lines of code as a baseline for databases we are analyzing.
@aeisenberg aeisenberg force-pushed the aeisenberg/add-github-linguist branch from d2b4652 to c4a84a9 Compare April 22, 2021 22:59
Copy link
Contributor

@robertbrignull robertbrignull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

As you say, this is just adding the library. So I wouldn't worry about the size of the PR. That's just an unfortunate side effect of having the node modules in the repository.

I don't really know if the upgrading of the package lock file is a problem or not, but I'm going to assume it's not. I still have an old version of npm and I tried checking out your branch and I could still do npm things without errors.

@aeisenberg aeisenberg marked this pull request as ready for review April 23, 2021 17:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants