Skip to content
View camchenry's full-sized avatar

Organizations

@oxc-project

Block or report camchenry

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Please don't include any personal information such as legal names or email addresses. Maximum 100 characters, markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
camchenry/README.md

Hi there 👋

My name is Cam McHenry. I'm a software engineer that is passionate about building great web applications. I'm currently working at GitHub. I sometimes write about TypeScript and React on my blog, as well as other general web topics.

Pinned Loading

  1. oxc-project/oxc Public

    ⚓ A collection of JavaScript tools written in Rust.

    Rust 13.9k 538

  2. resources Public

    Resources about engineering and leadership

    2

2,285 contributions in the last year

Contribution Graph
Day of Week March April May June July August September October November December January February March
Sunday
Monday
Tuesday
Wednesday
Thursday
Friday
Saturday
Less
No contributions.
Low contributions.
Medium-low contributions.
Medium-high contributions.
High contributions.
More

Activity overview

Contributed to oxc-project/oxc, actions/add-to-project, oxc-project/oxc-project.github.io and 17 other repositories
Loading A graph representing camchenry's contributions from March 17, 2024 to March 21, 2025. The contributions are 51% commits, 24% code review, 14% pull requests, 11% issues.

Contribution activity

March 2025

Created 1 repository

Created a pull request in oxc-project/oxc that received 5 comments

ci(benchmarks): try using walltime instrumentation

+38 −0 lines changed 5 comments
Opened 13 other pull requests in 3 repositories
Reviewed 31 pull requests in 2 repositories

Created an issue in octokit/plugin-retry.js that received 7 comments

[FEAT]: Requests returning HTTP 410 Gone should not be retried

Describe the need As part of the Projects (classic) sunset, these REST APIs are returning HTTP 410 to indicate that the APIs are no longer available.

1 task done
7 comments
Opened 5 other issues in 2 repositories
141 contributions in private repositories Mar 3 – Mar 21
Loading