Skip to content

Auto-generate available env categories list in README via xtask#188

Merged
Boshen merged 3 commits intomainfrom
copilot/update-readme-env-categories
Mar 23, 2026
Merged

Auto-generate available env categories list in README via xtask#188
Boshen merged 3 commits intomainfrom
copilot/update-readme-env-categories

Conversation

Copy link
Contributor

Copilot AI commented Mar 22, 2026

  • Add marker comments to README.md for auto-generated env categories section
  • Update xtask/src/main.rs to generate the env categories list and write it into README.md
  • Run the xtask to generate the initial README content
  • Verify the generated README content and idempotency
  • Run tests and linting to ensure nothing is broken
  • Fix formatting (cargo fmt) to pass CI
Original prompt

This section details on the original issue you should resolve

<issue_title>Update the README with the list of available, valid env categories</issue_title>
<issue_description>Add a section to the README with a list of all available globals categories: node, builtin, es2016, es2025, nodeBuiltin, etc.

This should be set up to be updated automatically as part of the script to regenerate the package files.</issue_description>

Comments on the Issue (you are @copilot in this section)


📍 Connect Copilot coding agent with Jira, Azure Boards or Linear to delegate work to Copilot in one click without leaving your project management tool.

Copilot AI changed the title [WIP] Update README with list of available env categories Auto-generate available env categories list in README via xtask Mar 22, 2026
Copilot AI requested a review from connorshea March 22, 2026 22:04
@connorshea
Copy link
Member

@copilot run the formatter to fix ci

Copy link
Contributor Author

Copilot AI commented Mar 22, 2026

@copilot run the formatter to fix ci

Fixed in b82d1b3 — ran cargo fmt to resolve the formatting issue in xtask/src/main.rs.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

  • dprint.dev
    • Triggering command: /usr/bin/curl curl -fsSL REDACTED (dns block)
  • plugins.dprint.dev
    • Triggering command: /home/REDACTED/.cargo/bin/dprint dprint fmt --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no --warn=unexpected_cfgs --allow=clippy::lint_groups_priority --allow=clippy::declare_interior_mutable_const --check-cfg cfg(crossbeam_loom) lib/�� cwnFzIl/symbols.--error-format=json d_script_build-6--json=diagnostic-rendered-ansi,artifacts,future-incompat bin/rustc lib/rustlib/x86_cc u.o 7076a90.rlib bin/rustc (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

Copy link
Member

@connorshea connorshea left a comment

Choose a reason for hiding this comment

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

LGTM!

@connorshea connorshea marked this pull request as ready for review March 22, 2026 22:57
@connorshea
Copy link
Member

@Boshen I'd like this added to the README so I can improve the env section in the Oxlint config docs by referencing it, is this okay?

@connorshea connorshea requested a review from Boshen March 22, 2026 23:09
@Boshen Boshen merged commit 9386201 into main Mar 23, 2026
2 checks passed
@Boshen Boshen deleted the copilot/update-readme-env-categories branch March 23, 2026 05:30
@Boshen Boshen mentioned this pull request Mar 22, 2026
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.

Update the README with the list of available, valid env categories

3 participants