Skip to content
View F3n67u's full-sized avatar

Organizations

@nodejs

Block or report F3n67u

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

Pinned Loading

  1. node Public

    Forked from nodejs/node

    Node.js JavaScript runtime ✨🐢🚀✨

    JavaScript 1

41 contributions in the last year

Contribution Graph
Day of Week December January February March April May June July August September October November December
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 LadybirdBrowser/ladybird, nodejs/node, angular/components and 10 other repositories
Loading A graph representing F3n67u's contributions from December 17, 2023 to December 22, 2024. The contributions are 40% pull requests, 37% commits, 17% code review, 6% issues.

Contribution activity

December 2024

Created 6 commits in 1 repository
Created 1 repository

Created a pull request in LadybirdBrowser/ladybird that received 4 comments

LibWeb: Ensure Headers API can handle non-ascii characters

Ensure the Headers object's associated header list is ISO-8859-1 encoded when set using Infra::isomorphic_encode and correctly decoded using Infra:…

+188 −13 lines changed 4 comments
Opened 6 other pull requests in 2 repositories
LadybirdBrowser/ladybird 4 merged 1 closed
w3c/clipboard-apis 1 open
Reviewed 2 pull requests in 1 repository
LadybirdBrowser/ladybird 2 pull requests

Created an issue in whatwg/fetch that received 2 comments

Empty statusText does not match the reason-phrase token production

What is the issue with the Fetch Standard? In initialize a response algorithm: If init["statusText"] does not match the reason-phrase token produ…

2 comments
Opened 1 other issue in 1 repository
whatwg/fetch 1 closed
Loading

Seeing something unexpected? Take a look at the GitHub profile guide.