Skip to content

docs: update new package name #38

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

Closed
wants to merge 1 commit into from
Closed

docs: update new package name #38

wants to merge 1 commit into from

Conversation

g-plane
Copy link
Contributor

@g-plane g-plane commented Jan 17, 2019

Just change to new package name.

Non-related question: how to join this organization? I'm interested in TypeScript and ESLint.

@codecov
Copy link

codecov bot commented Jan 17, 2019

Codecov Report

Merging #38 into master will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #38   +/-   ##
=======================================
  Coverage   93.77%   93.77%           
=======================================
  Files          11       11           
  Lines        1686     1686           
  Branches      376      376           
=======================================
  Hits         1581     1581           
  Misses         55       55           
  Partials       50       50

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ebe638b...3fc01e9. Read the comment docs.

@j-f1
Copy link
Contributor

j-f1 commented Jan 17, 2019

cc @JamesHenry

@JamesHenry
Copy link
Member

@g-plane The reason we held off on this is that that those instructions are not valid until we publish a version under that name.

We are working with the ESLint TSC on the timing of that. We'll update these docs as part of the release!

Non-related question: how to join this organization? I'm interested in TypeScript and ESLint.

We haven't figured out a nomination process or anything just yet, but we'd be really grateful for your contributions and will definitely invite consistently committed folks to join the team :)

Thanks!

@JamesHenry JamesHenry closed this Jan 17, 2019
JamesHenry pushed a commit that referenced this pull request Jan 17, 2019
JamesHenry pushed a commit that referenced this pull request Jan 17, 2019
JamesHenry pushed a commit that referenced this pull request Jan 18, 2019
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 21, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants