Skip to content
View nathanjmcdougall's full-sized avatar

Sponsoring

@cosmicBboy
@15r10nk

Organizations

@joinplex-dev

Block or report nathanjmcdougall

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. usethis-python Public

    Automate Python project setup and development tasks that are otherwise performed manually.

    Python 5 3

  2. geospatial-wheels-index Public

    A PEP503 compliant package index for cgohlke/geospatial-wheels Windows GIS wheel files

    Python 4

  3. rstudio/pins-python Public

    Python 57 11

  4. unionai-oss/pandera Public

    A light-weight, flexible, and expressive statistical data testing library

    Python 3.8k 332

1,090 contributions in the last year

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

Activity overview

Loading A graph representing nathanjmcdougall's contributions from April 28, 2024 to April 29, 2025. The contributions are 41% issues, 33% commits, 25% pull requests, 1% code review.

Contribution activity

April 2025

Created 1 repository

Created a pull request in nathanjmcdougall/usethis-python that received 5 comments

98 implement usethis tool import linter

+1,230 −96 lines changed 5 comments
Opened 75 other pull requests in 4 repositories
  • Fix typos
    This contribution was made on Apr 25
Reviewed 4 pull requests in 2 repositories

Created an issue in nathanjmcdougall/usethis-python that received 4 comments

Consider splitting get_associated_ruff_rules into two cases for managed and non-managed rules

Motivation Not all rules are managed, e.g. INP for import-linter. At the moment, it is tool-dependent whether the rules from get_associated_ruff_rules

4 comments
Opened 83 other issues in 2 repositories
Loading