Skip to content

docs(linter): always refer as "ES2015" instead of "ES6"#15411

Merged
graphite-app[bot] merged 1 commit intomainfrom
11-07-docs_linter_docs_always_refer_as_es2015_instead_of_es6_
Nov 7, 2025
Merged

docs(linter): always refer as "ES2015" instead of "ES6"#15411
graphite-app[bot] merged 1 commit intomainfrom
11-07-docs_linter_docs_always_refer_as_es2015_instead_of_es6_

Conversation

@sapphi-red
Copy link
Member

@sapphi-red sapphi-red commented Nov 7, 2025

It is now more common to refer ES6 / ES2015 as "ES2015" than "ES6". This PR updates multiple places to use "ES2015" instead of "ES6". It also removes some redundant "ES6" when it is not important anymore in context of those sentences.

Copy link
Member Author

sapphi-red commented Nov 7, 2025


How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • 0-merge - adds this PR to the back of the merge queue
  • hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

This stack of pull requests is managed by Graphite. Learn more about stacking.

@github-actions github-actions bot added A-linter Area - Linter C-docs Category - Documentation. Related to user-facing or internal documentation labels Nov 7, 2025
@sapphi-red sapphi-red force-pushed the 11-07-docs_linter_import_named_update_es7_comment_in_examples branch from 70ce273 to 94e57de Compare November 7, 2025 05:08
@sapphi-red sapphi-red force-pushed the 11-07-docs_linter_docs_always_refer_as_es2015_instead_of_es6_ branch from 0ec4501 to 622e999 Compare November 7, 2025 05:08
@sapphi-red sapphi-red requested a review from camc314 November 7, 2025 05:13
@sapphi-red sapphi-red marked this pull request as ready for review November 7, 2025 05:14
@sapphi-red sapphi-red force-pushed the 11-07-docs_linter_docs_always_refer_as_es2015_instead_of_es6_ branch from 622e999 to cd67a19 Compare November 7, 2025 05:14
@codspeed-hq
Copy link

codspeed-hq bot commented Nov 7, 2025

CodSpeed Performance Report

Merging #15411 will not alter performance

Comparing 11-07-docs_linter_docs_always_refer_as_es2015_instead_of_es6_ (a698927) with 11-07-docs_linter_import_named_update_es7_comment_in_examples (94e57de)

Summary

✅ 4 untouched
⏩ 33 skipped1

Footnotes

  1. 33 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports.

@camc314 camc314 added the 0-merge Merge with Graphite Merge Queue label Nov 7, 2025
Copy link
Contributor

camc314 commented Nov 7, 2025

Merge activity

It is now more common to refer ES6 / ES2015 as "ES2015" than "ES6". This PR updates multiple places to use "ES2015" instead of "ES6". It also removes some redundant "ES6" when it is not important anymore in context of those sentences.
@graphite-app graphite-app bot force-pushed the 11-07-docs_linter_import_named_update_es7_comment_in_examples branch from 94e57de to a0c5203 Compare November 7, 2025 10:14
@graphite-app graphite-app bot force-pushed the 11-07-docs_linter_docs_always_refer_as_es2015_instead_of_es6_ branch from a698927 to 2c6bd9e Compare November 7, 2025 10:14
Base automatically changed from 11-07-docs_linter_import_named_update_es7_comment_in_examples to main November 7, 2025 10:20
@graphite-app graphite-app bot removed the 0-merge Merge with Graphite Merge Queue label Nov 7, 2025
@graphite-app graphite-app bot merged commit 2c6bd9e into main Nov 7, 2025
21 checks passed
@graphite-app graphite-app bot deleted the 11-07-docs_linter_docs_always_refer_as_es2015_instead_of_es6_ branch November 7, 2025 10:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-linter Area - Linter C-docs Category - Documentation. Related to user-facing or internal documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments